This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: mutex in frame code
- To: mrs at wrs dot com (Mike Stump)
- Subject: Re: mutex in frame code
- From: Richard Earnshaw <rearnsha at arm dot com>
- Date: Mon, 01 Feb 1999 15:36:10 +0000
- Cc: jbuck at Synopsys dot COM, law at cygnus dot com, drepper at cygnus dot com, egcs at cygnus dot com
- Cc: richard dot earnshaw at arm dot com
- Organization: ARM Ltd.
- Reply-To: richard dot earnshaw at arm dot com
> > From: Joe Buck <jbuck@Synopsys.COM>
> > To: law@cygnus.com
> > Date: Tue, 26 Jan 99 9:54:36 PST
>
> > But for i386, we have -mcpu=x -march=y, and -mcpu for Intel means
> > the same as -mtune on Sparc! -march is used to generate code that
> > requires a particular processor.
>
> This is unfortunate. We need a command decision to bit the bullet and
> then to make the ports conform to this decision and document it.
> :-( My guess is the SPARC port is wrong and should be fixed.
Well on the ARM, -mcpu=<cpu> is short-hand for "-march=<archof(cpu)>
-mtune=cpu". It makes life a little more complicated for me, but much
easier for the user since only one option has to be given instead of two.