[superh-gnu-discuss] optimization problem with 4.4-200

[Andrew Stubbs]

Akira-san,

The Lite toolchains are configured for SH-4A only. We do not recommend
that you use them for SH-4.

However, you should find that the compiler "-m4" option to switch to
SH-4 mode is still available. Hopefully this will solve the problem you
are having.

Note that we do not provide SH-4 "-m4" configured libraries or C runtime
files, so the compiler will fall back to using the SH-4A versions of
those. However, you've already been using those at -O0 with success, so
simple programs should work, at least.

Hope that helps

Andrew

On 19/10/10 07:42, Akira Kobayashi wrote:
> Hello Andrew-san,
> 
> Thank you very much for your reply.
> I reconfirmed this problem after I received your reply.
> The board I used was SH4 core. We reconfirmed the problem with the board.
> However, as you said, the problem was not reproduced with the SH4A core 
> board.
> Thank you for correcting my mistake.
> 
> Best Regards,
> Akira
> 
> ----- Original Message ----- From: "Andrew Stubbs" <ams at codesourcery.com>
> To: "Akira Kobayashi" <koba at lineo.co.jp>
> Cc: <superh-gnu-discuss at codesourcery.com>
> Sent: Monday, October 18, 2010 10:55 PM
> Subject: Re: [superh-gnu-discuss] optimization problem with 4.4-200
> 
> 
>> On 18/10/10 14:03, Akira Kobayashi wrote:
>>> When compiling the attached code with optimization option (-O1, -O2,
>>> -O3, -Os), the result was different from the result of no optimization
>>> (-O0).
>>> Will this problem be fixed in the next release?
>>
>> I can't reproduce this problem with either 4.4-200, or the upcoming new
>> version. I have compiled your test case for Little Endian SH-4A, at all
>> optimization levels, and without any other options.
>>
>> Are you sure there's not something else happening here?
>>
>> In any case, the new Lite edition compiler (to be released in a few
>> weeks) will be based on GCC 4.5 - a major update, so I would be
>> surprised if it suffered from exactly the same problems.
>>
>> Thank you for reporting the problem.
>>
>> Andrew Stubbs
>> CodeSourcery 
>