This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
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
- References:
- ColdFire submission
- [ColdFire 1/63] Retabulate TARGET_CPU_CPP_BUILTINS
- [ColdFire 2/63] Use TUNE_* macros instead of TARGET_* macros
- [ColdFire 3/63] Add TUNE_68040_60
- [ColdFire 4/63] TARGET_COLDFIRE_FPU vs. TARGET_CFV4E
- [ColdFire 6/63] Make gcc honour -m68010
- [ColdFire 7/63] Default target selection and --with-cpu support
- [ColdFire 8/63] Share ASM_SPEC code between targets
- [ColdFire 9/63] Add -mcpu, -march, -mtune, and related options
- Re: [ColdFire 9/63] Add -mcpu, -march, -mtune, and related options
- Re: [ColdFire 9/63] Add -mcpu, -march, -mtune, and related options
- Re: [ColdFire 9/63] Add -mcpu, -march, -mtune, and related options