This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: mutex in frame code
- To: Joe Buck <jbuck at Synopsys dot COM>
- Subject: Re: mutex in frame code
- From: David Edelsohn <dje at watson dot ibm dot com>
- Date: Tue, 26 Jan 1999 13:56:21 -0500
- Cc: law at cygnus dot com, drepper at cygnus dot com, egcs at cygnus dot com
>>>>> Joe Buck writes:
Joe> Generally one would not specify an exact processor in -march, but it would
Joe> make sense in -mtune. -march says what instructions I can assume are
Joe> present (and possibly, what restrictions on instruction order for
Joe> processors without interlocks, what few that exist). -mtune says what
Joe> I should optimize for.
And -mcpu specifies an architecture / tuning pair instead of
confusing users and forcing uses to type multiple options where one option
is implied by the other.
POWER and PowerPC do not have evolving architectures. PPC604 is
not a superset of PPC603 which is not a superset of PPC601. "common" is a
special mode for AIX which runs on both POWER and PowerPC architectures,
but no one else does because neither is a a superset of the other.
Will you please try to understand that your clasification does not
apply equally well to all ports and you should not impose it upon everyone?
David