From: Ralf Baechle <ralf@linux-mips.org>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: linux-mips@linux-mips.org
Subject: Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA)
Date: Tue, 19 Aug 2003 05:38:43 +0200 [thread overview]
Message-ID: <20030819033843.GA6223@linux-mips.org> (raw)
In-Reply-To: <20030812140452.GD10792@rembrandt.csv.ica.uni-stuttgart.de>
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
next prev parent reply other threads:[~2003-08-19 3:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 6:26 GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA) Atsushi Nemoto
2003-08-12 6:49 ` Kumba
2003-08-12 7:06 ` Thiemo Seufer
2003-08-12 7:56 ` Kumba
2003-08-12 8:10 ` Thiemo Seufer
2003-08-12 8:26 ` Kumba
2003-08-12 9:25 ` Atsushi Nemoto
2003-08-19 3:52 ` Ralf Baechle
2003-08-12 6:51 ` Thiemo Seufer
2003-08-12 10:06 ` Atsushi Nemoto
2003-08-12 10:16 ` Thiemo Seufer
2003-08-12 15:26 ` Atsushi Nemoto
2003-08-14 3:03 ` Thiemo Seufer
2003-08-12 13:56 ` Maciej W. Rozycki
2003-08-12 14:04 ` Thiemo Seufer
2003-08-12 14:40 ` Maciej W. Rozycki
2003-08-14 3:08 ` Thiemo Seufer
2003-08-19 3:38 ` Ralf Baechle [this message]
2003-08-19 12:22 ` Maciej W. Rozycki
2003-08-19 12:34 ` Ralf Baechle
2003-08-19 3:57 ` Ralf Baechle
2003-08-19 6:41 ` Thiemo Seufer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030819033843.GA6223@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox