linux-mips
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: Co-Proc. 0

from [Ralf Baechle] [Permanent Link][Original]
To: Chris Fouts <ChrisF@SCC-INC.com>
Subject: Re: Co-Proc. 0
From: Ralf Baechle <ralf@linux-mips.org>
Date: Thu, 17 Jul 2003 04:30:30 +0200
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
In-reply-to: <4019CBE63D5A174F8F55FE25BC82D04102B46815@Mailserver.scc-inc.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <4019CBE63D5A174F8F55FE25BC82D04102B46815@Mailserver.scc-inc.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i 
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
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
  • Co-Proc. 0, Chris Fouts
    • Re: Co-Proc. 0, Ralf Baechle <=
Previous by Date:  Re: sudo oops on mips64 linux_2_4, Geert Uytterhoeven
Next by Date:  [PATCH] 2.4 Alchemy Power management., Liam Girdwood
Previous by Thread:  Co-Proc. 0, Chris Fouts
Next by Thread:  [PATCH][2.6.0-test1] Pb1500 PCI - Makefile rule typo, Liam Girdwood
Indexes:  [Date] [Thread] [Top] [All Lists]