All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@nildram.co.uk>
To: Thiemo Seufer <ths@networkno.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] MIPS COP1X (and related) instructions
Date: Sat, 29 Dec 2007 09:14:54 +0000	[thread overview]
Message-ID: <8763yh7tgx.fsf@firetop.home> (raw)
In-Reply-To: <20071229013338.GA18467@networkno.de> (Thiemo Seufer's message of "Sat\, 29 Dec 2007 01\:33\:38 +0000")

Thiemo Seufer <ths@networkno.de> writes:
> Richard Sandiford wrote:
>> All MIPS COP1X instructions currently require the FPU to be in 64-bit
>> mode.  My understanding is that this is too restrictive, and that the
>> base conditions are different for different revisions of the ISA:
>> 
>>   MIPS IV:
>>     COP1X instructions are available when the XX (CU3) bit of the
>>     status register is set.  This bit can be set independently of
>>     UX and FR, and controls the core MIPS IV instructions as well
>>     as the FPU ones.
>
> This part is, sadly, not fully correct. It depends on the CPU
> implementation what effect, the CU3 bit has. IIRC it behaves on some
> CPUs as you describe, while it is a nop on others.

Sorry.  I'll take your word for it.

> (I don't know offhand which CPU did what there.)

(FWIW, the r10k and VR5500 do as described, and I'm pretty sure the
RM7000 and RM9000 did too.)

> Looks reasonable to me, apart from that one misassumption.

What should the patch do instead for MIPS IV?  Enable them unconditionally?

Richard

  reply	other threads:[~2007-12-29  9:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28 12:13 [Qemu-devel] MIPS COP1X (and related) instructions Richard Sandiford
2007-12-29  1:33 ` Thiemo Seufer
2007-12-29  9:14   ` Richard Sandiford [this message]
2007-12-29 18:47     ` Thiemo Seufer
2007-12-30  7:54       ` Richard Sandiford

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=8763yh7tgx.fsf@firetop.home \
    --to=rsandifo@nildram.co.uk \
    --cc=qemu-devel@nongnu.org \
    --cc=ths@networkno.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.