From: Ralf Baechle <ralf@linux-mips.org>
To: Colin.Helliwell@Zarlink.Com
Cc: linux-mips@linux-mips.org
Subject: Re: MIPS32/MIPS4K kernel compilation settings
Date: Mon, 7 Oct 2002 14:18:44 +0200 [thread overview]
Message-ID: <20021007141844.A9410@linux-mips.org> (raw)
In-Reply-To: <OFFFD113F8.B40CC667-ON80256C4B.0028865D@zarlink.com>; from Colin.Helliwell@Zarlink.Com on Mon, Oct 07, 2002 at 08:48:26AM +0100
On Mon, Oct 07, 2002 at 08:48:26AM +0100, Colin.Helliwell@Zarlink.Com wrote:
> Was just wondering why the (2.4.19) kernel compilation for MIPS4K systems
> appears to be using the "-mips2" compiler setting - shouldn't it be using
> -mips4 or -mips32 to get the full instruction set?
Because we want MIPS II only ;-)
There are serious problems with the use of 64-bit stuff in the 32-bit
kernel, so we can't use mips3, mips4 or mips64. -mips32 works but is not
supported by all toolchains. Anyway, mips32 doesn't deliver much that isn't
already part of MIPS II.
Ralf
prev parent reply other threads:[~2002-10-07 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 7:48 MIPS32/MIPS4K kernel compilation settings Colin.Helliwell
2002-10-07 12:18 ` Ralf Baechle [this message]
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=20021007141844.A9410@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Colin.Helliwell@Zarlink.Com \
--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