[m68k] Convert CPP_SPEC to TARGET_CPU_CPP_BUILTINS

Bernardo Innocenti bernie@develer.com
Wed Sep 17 16:47:00 GMT 2003


Ralf Corsepius wrote:

>>  You could define __mc68030__ on your own when you really need it.
> 
> No. __mc68030__ is used in multilib'ed parts of RTEMS, therefore it must
> be defined in gcc, even if it doesn't make a different in GCC's code
> generation.
> 
> As last resort we might be able to supply it inside of an RTEMS specific
> TARGET_OS_CPP_SPEC or similar.
> 
> However, I really don't understand why you don't want to support an
> -m68030 which internally is identical to -m68020 -D__m68030__.

We all thought nobody would be interested in telling the difference
between '020 and '030. The compiler doesn't care and the Linux kernel
doesn't care either.

Now we know that it matters for RTEMS, therefore I'll post a patch to
add it back. It makes the code a little bit uglier, but if it's needed
then it's worth doing.

-- 
  // Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/  http://www.develer.com/

Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html





More information about the Gcc-patches mailing list