From: Ralf Baechle <ralf@linux-mips.org>
To: Chris Fouts <ChrisF@SCC-INC.com>
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: Co-Proc. 0
Date: Thu, 17 Jul 2003 04:30:30 +0200 [thread overview]
Message-ID: <20030717023030.GA2378@linux-mips.org> (raw)
In-Reply-To: <4019CBE63D5A174F8F55FE25BC82D04102B46815@Mailserver.scc-inc.com>
On Wed, Jul 16, 2003 at 09:11:22AM -0400, Chris Fouts wrote:
> What options do I use for the compiler to recoginze the C0 specific
> op-codes,
> e.g., mfc0, mtc0, etc? I tried -mips1, -mips2, -mips3 and arch=RM7000 to no
> avail.
No options needed at all.
Ralf
prev parent reply other threads:[~2003-07-17 2:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 13:11 Co-Proc. 0 Chris Fouts
2003-07-17 2:30 ` 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=20030717023030.GA2378@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ChrisF@SCC-INC.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