From: Jeroen Hofstee <jeroen@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot Bug with newer GCC
Date: Sat, 02 Feb 2013 11:18:44 +0100 [thread overview]
Message-ID: <510CE804.7020600@myspectrum.nl> (raw)
In-Reply-To: <510CD045.8050207@denx.de>
Hello,
On 02/02/2013 09:37 AM, Heiko Schocher wrote:
> Hello Wolfgang, Sebastian,
>
> On 01.02.2013 12:31, Wolfgang Denk wrote:
>> In message <E70AF999396FDF4EAE40E195B847096109F5D3A9@SRVEXCH-2K10.CADCON.INTERN> you wrote:
>>> we are using u-boot in our embedded system with arm-1136jfs cpu.
>> Which exact system / board configuration is this?
>>
>> And which exact U-Boot version (git commit ID ?) is it?
>>
>>> We recently tried a new toolchain with GCC 4.7.2.
>>> If compiled with the new toolchain the feature CONFIG_AUTO_COMPLETE isn't working.
>> We have been using GCC 4.7.2 for several months now, on many systems.
>> No such problems have been reported before, so I speculate if this is
>> really a problem with mainline code?
> Sebastian wrote On 01.02.2013 08:55:
>> we are using u-boot in our embedded system with arm-1136jfs cpu.
>> We recently tried a new toolchain with GCC 4.7.2.
>> If compiled with the new toolchain the feature CONFIG_AUTO_COMPLETE isn't working.
>> U-Boot start normally and on hitting TAB the system freezes.
>> I tracked the problem down the variables __u_boot_cmd_start and __u_boot_cmd_end. Both are not valid with the new toolchain. And accessing one results in a system freeze.
>> Probably the is a problem in arch/arm/cpu/u-boot.lds. I really bad at linker scripts.
> I just see some problems with ll_entry_* functions described in my
> post here:
> http://lists.denx.de/pipermail/u-boot/2013-February/145711.html
>
> I do not know, if this is the same problem, as I face problems only
> before relocation, after relocation all works fine ...
>
> In this thread Marek wrote, that for this problem albert has
> a solution ... (CCed albert and marek)
>
> Albert? Can you help here?
I am tempted to think that is unrelated. First of all since you encounter
problems with the 4.6 toolchain. This trap is not present when
compiling with a 4.6 version (at least not for me).
Second, because I bothered Marex and Albert already with this
problem on irc and they concluded it could not be ll related.
Third, because dumping the array of commands to a console,
displays them all correctly.
Regards,
Jeroen
next prev parent reply other threads:[~2013-02-02 10:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 7:55 [U-Boot] U-Boot Bug with newer GCC Priebe, Sebastian
2013-02-01 11:31 ` Wolfgang Denk
2013-02-01 17:41 ` Jeroen Hofstee
2013-02-01 21:42 ` Wolfgang Denk
2013-02-02 11:25 ` Jeroen Hofstee
[not found] ` <E70AF999396FDF4EAE40E195B847096109F5D6FD@SRVEXCH-2K10.CADCON.INTERN>
2013-02-01 21:36 ` Wolfgang Denk
2013-02-02 8:37 ` Heiko Schocher
2013-02-02 10:18 ` Jeroen Hofstee [this message]
2013-02-02 11:32 ` Albert ARIBAUD
2013-02-02 14:05 ` Jeroen Hofstee
2013-02-02 15:05 ` Marek Vasut
2013-02-02 21:23 ` Wolfgang Denk
2013-02-02 21:22 ` Wolfgang Denk
2013-02-02 21:44 ` Jeroen Hofstee
2013-02-04 7:11 ` Priebe, Sebastian
2013-02-04 8:49 ` Albert ARIBAUD
2013-02-04 11:28 ` Priebe, Sebastian
2013-02-04 11:35 ` Albert ARIBAUD
2013-02-04 14:23 ` Priebe, Sebastian
2013-02-04 14:32 ` Albert ARIBAUD
2013-02-04 15:32 ` Priebe, Sebastian
2013-02-04 20:49 ` Wolfgang Denk
2013-02-02 15:43 ` Jeroen Hofstee
2013-02-02 17:38 ` Heiko Schocher
2013-02-02 16:50 ` Marek Vasut
2013-02-02 19:12 ` Jeroen Hofstee
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=510CE804.7020600@myspectrum.nl \
--to=jeroen@myspectrum.nl \
--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