This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Disable building with i386-*, -march=i386 or -mcpu=i386.
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, GNU C Library <libc-alpha at sourceware dot org>, Andreas Jaeger <aj at suse dot com>, Thomas Schwinge <thomas at codesourcery dot com>
- Date: Tue, 09 Apr 2013 08:02:28 -0400
- Subject: Re: [PATCH] Disable building with i386-*, -march=i386 or -mcpu=i386.
- References: <513FE49D dot 3050406 at redhat dot com> <Pine dot LNX dot 4 dot 64 dot 1303131610540 dot 19781 at digraph dot polyomino dot org dot uk> <51526E77 dot 4040801 at redhat dot com> <Pine dot LNX dot 4 dot 64 dot 1303271431550 dot 23096 at digraph dot polyomino dot org dot uk> <5154668A dot 6000700 at redhat dot com> <5160465E dot 8060400 at redhat dot com> <20130408210918 dot D97632C074 at topped-with-meat dot com> <51634DE2 dot 1060109 at redhat dot com> <20130408231128 dot DA09C2C0A2 at topped-with-meat dot com>
On 04/08/2013 07:11 PM, Roland McGrath wrote:
>> That's true, and I'm willing to make it hard error if that's what
>> people think we should actually do.
>
> It's my preference, but I don't insist on it.
Preference noted. I'd like to leave it as-is to help new developers
on such systems, and to assist downstream. While I agree that on
principle it should be a hard error, the practical side of me says
that it helps more than it hinders to do the elision.
There is a "hard-line" somewhere in my decision making process, but
it's something I try hard *not* to listen to. It may be the case that
our decisions are a continual hegellian dialectic, and that the
community really can't do without you Roland ;-)
I mention again that it would be an additional enhancement to add
--march=i686 when configuring for i686-* to avoid problems with
users that have compilers defaulting to i386 code generation.
>> Even if you disagree that downstream should not be a reason, what
>> about budding developers that want to get started hacking GNU and
>> for some reason or another their system target triplet is i386-*
>> and everything breaks. I'd rather just commute that to i686-* and
>> have them happy little hackers :-)
>>
>> The BZ's we have fixed with this issue are all about novice developers
>> needing help or a configure error to tell them to do the right thing.
>
> A hard configure error should certainly tell them the right thing to do.
Agreed, all such hard configure errors should say why it failed and what
you should do to fix it with examples.
Cheers,
Carlos.