This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: egcs 2.91.66 ix86 problems...
- To: Richard Henderson <rth at twiddle dot net>
- Subject: Re: egcs 2.91.66 ix86 problems...
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 22 Jun 1999 01:44:16 -0600
- cc: Cristian Gafton <gafton at redhat dot com>, egcs-patches at egcs dot cygnus dot com
- Reply-To: law at cygnus dot com
In message <19990621223040.E30898@twiddle.net>you write:
> > A common sense rule says that using -mcpu=i486 should *not* define
> > __i486__, because we don't want to use i486 specific code, we are only
> > interested in the scheduler modifications.
>
> I second the motion that this is a bug in gcc. Any one else?
Well, the other interpretation is that those defines can be used by the
user to select one of N code sequences which work across the various
machines.
ie, it's entirely possible (even probable) that folks are using the -Dx86
options to trigger sequences optimized for one cpu or another. In fact,
I think glibc might do this (this is what inspired Jan to add defines when
optimizing for the AMD chips.
And there's another group that is likely using them for ISA selection.
Really we need *two* flags, one pass along the -marh= and another to pass
along -mcpu= as defines the user can check. That removes the ambiguity
we currently have.
jeff