Re: default CPU target ix86 based ports

2003-08-15 Thread Matthias Klose
Nathanael Nerode writes: > >Looking at config.gcc the TARGET_CPU_DEFAULT is > >overwritten by the target_alias. Looking at i386.c:1038 the cpu string > >(tuning) is set to the TARGET_DEFAULT, but the arch string remains at > >i386. the correct way to tune for i686 and use insn for i486 seems to > >

Re: default CPU target ix86 based ports

2003-08-11 Thread Nathanael Nerode
>> There's no good reason to drop 486 support under Linux. So for Linux, >> it would be -mcpu=i486 -mtune-i686 as the default, correct? > >yes, except gcc-3.3 doesn't have -mtune. So this should be -mcpu=i686 >-march=486. Aaargh. ;-) For 3.4 and the future we've standardized on 'arch' and 'tu

Re: default CPU target ix86 based ports

2003-08-09 Thread Matthias Klose
Nathanael Nerode writes: > Matthias Klose wrote: > >so make -mcpu=i586 -mtune=i686 the default? anything else as the > >default? > > Just to clarify, that would be the default for *hurd* only, right? yes > There's no good reason to drop 486 support under Linux. So for Linux, > it would be -mcp

Re: default CPU target ix86 based ports

2003-08-07 Thread Nathanael Nerode
Matthias Klose wrote: >Marcus Brinkmann writes: >> On Wed, Aug 06, 2003 at 10:05:13AM +0200, Matthias Klose wrote: >> > IIRC the Hurd can be built for i586 only, so it could be used as >the >> > default target CPU as well. >> >> We only require a coprocessor, but anything < i586 doesn't make much