From: Thiemo Seufer <ths@networkno.de>
To: qemu-devel@nongnu.org, rsandifo@nildram.co.uk
Subject: Re: [Qemu-devel] MIPS COP1X (and related) instructions
Date: Sat, 29 Dec 2007 18:47:15 +0000 [thread overview]
Message-ID: <20071229184714.GB18467@networkno.de> (raw)
In-Reply-To: <8763yh7tgx.fsf@firetop.home>
Richard Sandiford wrote:
> 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?
Given that it is currently theoretical, as the only MIPS IV CPU
supported is the VR5432: Add a comment to the MIPS IV test that it is
too restrictive for some CPUs.
Thiemo
next prev parent reply other threads:[~2007-12-29 18:47 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
2007-12-29 18:47 ` Thiemo Seufer [this message]
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=20071229184714.GB18467@networkno.de \
--to=ths@networkno.de \
--cc=qemu-devel@nongnu.org \
--cc=rsandifo@nildram.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).