This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc 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: [PATCH] Disable building with i386-*, -march=i386 or -mcpu=i386.


On Thu, 28 Mar 2013, Carlos O'Donell wrote:

> On 03/27/2013 10:35 AM, Joseph S. Myers wrote:
> > On Tue, 26 Mar 2013, Carlos O'Donell wrote:
> > 
> >> +# Configure for i686 if the user asks for i386. We don't support
> >> +# i386 any more but it continues to be common for users to configure
> >> +# 32-bit x86 as i386. We build for i686 instead.
> >> +if test "$machine" = i386; then
> >> +  machine="i686"
> > 
> > Wouldn't i486 be more conservative?
> 
> It would be, but in truth *everyone* I've talked to wants i686.
> 
> The distros build for i686, users use i686, there is no real use
> of i486 or i586 that I can see.

Is it really common for people to configure for i386 at all, rather than 
explicitly i686?  One option would simply be to give an error.

> Therefore I would like the elision of i386 to be to a value i686
> which has real value for users and is a sensible default in 99%
> of the cases. Defaulting to i486 or i586 might be more conservative
> but is less useful.
> 
> What do you think? Is it valid to balance usefullness in this way?

What do other architectures do, when configuring for generic versions of 
the architecture name?

> I agree. I'd actually like to rename i386 to x86 and merge i486 down
> in two steps.

ix86?  x86 is taken for things shared between 32-bit and 64-bit....

-- 
Joseph S. Myers
joseph@codesourcery.com


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