| To: | linux-mips@linux-mips.org |
|---|---|
| Subject: | Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA) |
| From: | Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de> |
| Date: | Tue, 12 Aug 2003 16:04:52 +0200 |
| In-reply-to: | <Pine.GSO.3.96.1030812155517.7029C-100000@delta.ds2.pg.gda.pl> |
| 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> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.4i |
Maciej W. Rozycki wrote: > On Tue, 12 Aug 2003, Thiemo Seufer wrote: > > > If the intention is to use mfc0 for 32bit kernels and dmfc0 for 64bit, > > the check should probably be > > > > #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. Thiemo |
| Previous by Date: | Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA), Maciej W. Rozycki |
|---|---|
| Next by Date: | Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA), Maciej W. Rozycki |
| Previous by Thread: | Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA), Maciej W. Rozycki |
| Next by Thread: | Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA), Maciej W. Rozycki |
| Indexes: | [Date] [Thread] [Top] [All Lists] |