public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Miao Qingjun <qmiao@centecnetworks.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot 1.1.4 compiled by eldk 4.1 for mpc82xx crashed
Date: Tue, 20 Mar 2007 10:19:15 +0800	[thread overview]
Message-ID: <45FF44A3.4010705@centecnetworks.com> (raw)
In-Reply-To: <45FE9482.8030008@smiths-aerospace.com>

Thanks very much.

I tried it using "-O0" and it's OK.
I think u-boot 1.1.4 is not gcc 4.0 friendly.
And I will try u-boot 1.2.0 recommended by Wolfgang Denk.


Jerry Van Baren ??:
> Miao Qingjun wrote:
>   
>> Hi,
>>
>> I encountered a big problem that u-boot 1.1.4 compiled by eldk 4.1 for
>> mpc82xx crashed.
>>
>> But if I build it using gcc-3.4.6 based cross tools, u-boot on my board
>> boots correctly.
>>
>> u-boot built by eldk 4.1 (gcc-4.0) failed, nothing occures on serial
>> port.
>>
>> Somebody sufered the same problem?
>>     
>
> This is often a missing "volatile" qualifier on shared variable
> (particularly hardware registers) references.  Newer compiler versions
> optimize more aggressively, making missing "volatile"s visible.
>
> If you use -O0 (no optimization) does it fix the problem?  If it does,
> it most likely is an optimization/volatile issue.  The hard part is to
> figure out where.  Device handling and board-specific code is the place
> to start.
>
> Best regards,
> gvb
>
>
>   

      reply	other threads:[~2007-03-20  2:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19 12:02 [U-Boot-Users] u-boot 1.1.4 compiled by eldk 4.1 for mpc82xx crashed Miao Qingjun
2007-03-19 12:28 ` Wolfgang Denk
2007-03-19 12:37   ` Miao Qingjun
2007-03-19 13:10     ` Wolfgang Denk
2007-03-19 13:47 ` Jerry Van Baren
2007-03-20  2:19   ` Miao Qingjun [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=45FF44A3.4010705@centecnetworks.com \
    --to=qmiao@centecnetworks.com \
    --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