This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [ColdFire 9/63] Add -mcpu, -march, -mtune, and related options


Roman Zippel <zippel@linux-m68k.org> writes:
>> I'm just hand-waving though.  You know what's appropriate for 680x0
>> better than I do, so if you think they should be treated differently
>> from ColdFire, I can take the default float setting for 680x0 targets
>> from the float setting for the default CPU, rather than the chosen CPU.
>
> For Linux it doesn't really matter, what I have in mind is that a generic 
> target like m68k-elf could be used with --with-float=soft.

But what precisely do you think the semantics should be?
Like I say, I think it's reasonable to use the device defaults
for ColdFire, as -mhard-float does not change the calling conventions.
Are you saying that you disagree, and that you think the default should
be decided by the configuration regardless of -mcpu?  Or are you saying
that the default should be decided in a different way for 680x0 and
ColdFire targets?

Richard


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]