From: Eric Christopher <echristo@redhat.com>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: "H . J . Lu" <hjl@lucon.org>, cgd@broadcom.com, linux-mips@oss.sgi.com
Subject: Re: linux.h patch for mips
Date: 26 May 2002 11:00:54 -0700 [thread overview]
Message-ID: <1022436056.29700.3.camel@ghostwheel.cygnus.com> (raw)
In-Reply-To: <20020525181404.GI21557@rembrandt.csv.ica.uni-stuttgart.de>
>
> At least for completeness there should be also _MIPS_ISA_MIPS5
> (the -mips5 swich would cause _MIPS_ISA_MIPS1 otherwise).
Rather irrelevent since mips5 really isn't supported in gcc, but ok. I
was more concerned with the kernel issues and how checks for processor
features was being done. Requiring -mipsX for anything isn't a good idea
(what if you want to compile for something that is not a particular
architecture, e.g. -march=r4600).
-eric
--
I will not carve gods
next prev parent reply other threads:[~2002-05-26 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1022278283.25829.46.camel@ghostwheel.cygnus.com>
2002-05-25 2:03 ` linux.h patch for mips H . J . Lu
2002-05-25 18:14 ` Thiemo Seufer
2002-05-26 18:00 ` Eric Christopher [this message]
2002-05-26 18:29 ` Thiemo Seufer
2002-05-27 6:55 ` Eric Christopher
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=1022436056.29700.3.camel@ghostwheel.cygnus.com \
--to=echristo@redhat.com \
--cc=cgd@broadcom.com \
--cc=hjl@lucon.org \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=linux-mips@oss.sgi.com \
/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