From: "Maik Hänig" <maik.haenig@s2000.tu-chemnitz.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Compiler Question
Date: Mon, 07 Feb 2011 11:24:44 +0100 [thread overview]
Message-ID: <4D4FC86C.2080003@hrz.tu-chemnitz.de> (raw)
In-Reply-To: <20110207101742.64D3BEC91C8@gemini.denx.de>
Dear Wolfgang Denk,
should I better use gcc 4.4?
And yes I'm working on ARM.
Best regards / Mit freundlichen Gr??en
Maik H?nig
Am 07.02.2011 11:17, schrieb Wolfgang Denk:
> Dear =?UTF-8?B?TWFpayBIw6RuaWc=?=,
>
> In message<4D4FBEAD.1030703@hrz.tu-chemnitz.de> you wrote:
>>
>> If I compile the same uboot with gcc 4.5.2, binutils 2.11 and glibc 2.13
>> the uboot compiles also successfully but it didn't work on the taget
>> system. The uboot don't have any outputs on the debug console.
>
> There are a number of known (and probably more unknown) compiler bugs
> in GCC 4.5.x.
>
> Workarounds for some of them have been added recently in mainline, so
> you might try switching to current top of tree instead (especially if
> you're on an ARM system).
>
> Best regards,
>
> Wolfgang Denk
>
next prev parent reply other threads:[~2011-02-07 10:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 3:08 [U-Boot] [U-BOOT] [PATCH] env: reduce the stack footprint for the env buf Lei Wen
2011-02-04 20:31 ` Scott Wood
2011-02-04 21:18 ` Wolfgang Denk
2011-02-05 1:21 ` Lei Wen
2011-02-05 8:30 ` Wolfgang Denk
2011-02-05 9:33 ` Graeme Russ
2011-02-05 14:11 ` Wolfgang Denk
2011-02-06 15:25 ` Lei Wen
2011-02-06 16:08 ` Wolfgang Denk
2011-02-07 4:38 ` Lei Wen
2011-02-07 5:04 ` Graeme Russ
2011-02-07 7:06 ` Wolfgang Denk
2011-02-07 6:58 ` Wolfgang Denk
2011-02-07 8:17 ` Lei Wen
2011-02-07 8:59 ` Wolfgang Denk
2011-02-07 9:01 ` Lei Wen
2011-02-07 9:43 ` [U-Boot] Compiler Question Maik Hänig
2011-02-07 10:17 ` Wolfgang Denk
2011-02-07 10:24 ` Maik Hänig [this message]
2011-02-07 11:41 ` Wolfgang Denk
2011-02-07 12:03 ` Maik Hänig
2011-02-07 13:10 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D4FC86C.2080003@hrz.tu-chemnitz.de \
--to=maik.haenig@s2000.tu-chemnitz.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox