linux-mips
[Top] [All Lists]

Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA)

To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Subject: Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA)
From: Ralf Baechle <ralf@linux-mips.org>
Date: Tue, 19 Aug 2003 05:38:43 +0200
Cc: linux-mips@linux-mips.org
In-reply-to: <20030812140452.GD10792@rembrandt.csv.ica.uni-stuttgart.de>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20030812065118.GD23104@rembrandt.csv.ica.uni-stuttgart.de> <Pine.GSO.3.96.1030812155517.7029C-100000@delta.ds2.pg.gda.pl> <20030812140452.GD10792@rembrandt.csv.ica.uni-stuttgart.de>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Tue, Aug 12, 2003 at 04:04:52PM +0200, Thiemo Seufer wrote:

> > > #ifdef __mips64
> > > # define MFC0             dmfc0
> > > # define MTC0             dmtc0
> > > #else
> > > # define MFC0             mfc0
> > > # define MTC0             mtc0
> > > #endif
> > 
> >  I'd go for CONFIG_MIPS64 here.
> 
> This would work as well, but I prefer compiler intrinsic defines
> over custom configury.

I agree for this particular header file because it's been copied into
user applications.  So ideally it should be able to live entirely without
CONFIG_* symbols rsp. <linux/config.h>.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>