From: Pete Popov <ppopov@pacbell.net>
To: "Kevin D. Kissell" <kevink@mips.com>, Ralf Baechle <ralf@uni-koblenz.de>
Cc: linux-mips@oss.sgi.com
Subject: r4600 flag
Date: Mon, 30 Jul 2001 22:55:35 -0700 [thread overview]
Message-ID: <3B664857.4040100@pacbell.net> (raw)
in arch/mips/Makefile, we use the -mcpu=r4600 flag for MIPS32. What's
interesting is that the use of this flag can cause the toolchain to
generate incorrect code. For example:
la k0, 1f
nop
1: nop
The la macro is split into a lui and a daddiu. The daddiu is not correct
for a mips32 cpu. Getting rid of the -mcpu=4600 fixes the problem and
the daddiu is then changed addiu.
Is there a truly correct -mcpu option for a mips32 cpu?
Pete
next reply other threads:[~2001-07-31 5:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 5:55 Pete Popov [this message]
2001-07-31 7:28 ` r4600 flag Thiemo Seufer
2001-07-31 9:25 ` Ralf Baechle
2001-07-31 12:58 ` Thiemo Seufer
2001-07-31 13:38 ` Carsten Langgaard
2001-07-31 15:29 ` John D. Davis
2001-08-02 11:54 ` Ralf Baechle
2001-07-31 8:06 ` Kevin D. Kissell
2001-07-31 8:06 ` Kevin D. Kissell
2001-07-31 9:31 ` Ralf Baechle
2001-07-31 11:40 ` Kevin D. Kissell
2001-07-31 11:40 ` Kevin D. Kissell
2001-07-31 13:08 ` 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=3B664857.4040100@pacbell.net \
--to=ppopov@pacbell.net \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@uni-koblenz.de \
/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