This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [m68k] Convert CPP_SPEC to TARGET_CPU_CPP_BUILTINS
- From: Joel Sherrill <joel dot sherrill at OARcorp dot com>
- To: Bernardo Innocenti <bernie at develer dot com>
- Cc: Gunther Nikl <gni at gecko dot de>, gcc-patches at gcc dot gnu dot org
- Date: Tue, 16 Sep 2003 07:49:17 -0500
- Subject: Re: [m68k] Convert CPP_SPEC to TARGET_CPU_CPP_BUILTINS
- Organization: OAR Corporation
- References: <3F64F6A2.5030204@develer.com> <jer82ipjtt.fsf@sykes.suse.de> <3F65BB28.3060004@develer.com> <20030915144423.GA30190@lorien.int.gecko.de> <3F6616A9.8020601@develer.com>
Hi,
I don't normally follow gcc-patches but Ralf Corsepius spotted
this one and I thought I should comment from an RTEMS perspective.
So far, we have spotted the following that matter to RTEMS.
mc68030: We use this to distinguish 68030 from the 68020+FPU and
68040. There are some subtle differences that matter.
mc68060: It just disappeared. Needs to stay in.
mcpu32: I can't think you are changing anything here but I have
never thought it correct that mcpu32 implies that mc68332 is
defined. There are other cpu32 CPU models and mc68332 implies
a certain memory map and set of peripherals that is not always
there.
There is also a cpu32+ in the mc68360 which is subtly different
but gcc does not recognize it as distinct.
--
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