From mboxrd@z Thu Jan  1 00:00:00 1970
From: Miao Qingjun <qmiao@centecnetworks.com>
Date: Tue, 20 Mar 2007 10:19:15 +0800
Subject: [U-Boot-Users] u-boot 1.1.4 compiled by eldk 4.1 for mpc82xx
 crashed
In-Reply-To: <45FE9482.8030008@smiths-aerospace.com>
References: <45FE7BD7.2000506@centecnetworks.com>
	<45FE9482.8030008@smiths-aerospace.com>
Message-ID: <45FF44A3.4010705@centecnetworks.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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
>
>
>