public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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 20:12:42 +0100	[thread overview]
Message-ID: <510D652A.5090503@myspectrum.nl> (raw)
In-Reply-To: <510D3427.9040001@myspectrum.nl>

Hello,

On 02/02/2013 04:43 PM, Jeroen Hofstee wrote:
>
>>> 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.
>>>
>> 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).
>>
Well, that turned out to be wrong, don't know exactly why, but it
is related. Perhaps because it is not a toolchain issue I took it for,
but slightly different placement between the different compiler
versions.
>> Second, because I bothered Marex and Albert already with this
>> problem on irc and they concluded it could not be ll related.
>>
It might be that code running before relocation could corrupt
the data used after relocation. Which would flaw the argument,
"after relocation ll should be fine".
>> Third, because dumping the array of commands to a console,
>> displays them all correctly.
>
> For completeness, the third statement is wrong. It is only the case
> for the working version, the table has incorrect values for
> cmdtp->name in current master. So lets hope it is the same problem.
> I will wait for Albert his patch and check again. Thanks for the pointer.
>
So it seems to be, that patch at least solves this issue.
Sebastian: can you check if this is resolved also resolved for your board
after applying http://patchwork.ozlabs.org/patch/217695/

Regards,
Jeroen

      parent reply	other threads:[~2013-02-02 19:12 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
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 [this message]

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=510D652A.5090503@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