This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: New target for Coldfire v4e?
>>> If people would buy into the concept so its not all wasted work, then
>>> yes, I'd pull all the ColdFire bits out of gcc/config/m68k and place
>>> them in gcc/config/coldfire.
>>
>>
>> We're talking about slimming m68k.md by about 500 lines here and
>> simplifying m68k.c in many places. That would be yummie.
>>
>> However, I'm concerned about code duplication. Many bugs would
>> certainly still affect both backends and many improvements would
>> be applicable to both.
>>
>> Couldn't we "split" the m68k backend in three parts instead?
>> A core part (m68k) containing all common code and two backends
>> based on it: m680x0 and coldfire. (CPU32 would stay with the
>> 68000 of course).
>>
>> This would require slightly more work initially, but it would
>> reduce maintenance costs in the long term.
>>
>
>I have been following this and want to make sure I am understanding.
>
>Would there now be separate m68k and coldfire targets? Said another
>way, would m68k-XYZ be able to include Coldfire support?
The suggestion as I put it forth would be no. You have sepperate
tools, one --target=m68k-xyz for the m68k family, and
--target=coldfire-xyz for the ColdFire family.
--
Peter Barada
peter@the-baradas.com