This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Illegal code generation: gcc-3.2 --target=m68k-elf
Peter Barada wrote:
>
> >This weekend, an RTEMS user reported a minor nit in
> >m68k/t-crtstuff which is causing bogus code on Coldfires.
> >It should be simple to fix and I think it rates being in the
> >upcoming release. I have filed PR8314 on it with a 1st
> >(broken) cut of a patch but I think this is more appropriate.
>
> Unfortunately this patch doesn't fix the problem that I'm seeing
> (target/8309).
This looks like a different bug than the one I am trying to fix.
There was a mistake in the patch I posted. The correct version
is in my latest feedback to PR8314. I think this is a critical
patch for 3.2.1. It's correctness (finally) is easy to verify.
It installed multilib versions of the crt* code and the m5200
did not use a bsr instruction.
There is an RTEMS coldfire user trying to put together a cut down
for the problem he describes as:
> <ii> is a counter declared <short int> and used in a <for()> instruction. gcc3.2 put it in frame position -10(a6).
> As you can see in 1E85E it is treated as word but.... in in 1E8A0 it is used as long : <add.l> !!!!
> in 1E8A8 the test of end loop is made correctly as short! The result is that loop controlled by <ii> never finish!
>
Does this look familiar by any chance?
> --
> Peter Barada Peter.Barada@motorola.com
> Wizard 781-852-2768 (direct)
> WaveMark Solutions(wholly owned by Motorola) 781-270-0193 (fax)
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985