From: John Baldwin <jhb@freebsd.org>
To: "Maciej W. Rozycki" <macro@imgtec.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Look for FIR in the last FreeBSD/mips floating-point register.
Date: Tue, 13 Jun 2017 16:43:00 -0000 [thread overview]
Message-ID: <2960345.dAXMQc0yB8@ralph.baldwin.cx> (raw)
In-Reply-To: <alpine.DEB.2.00.1706122119360.21750@tp.orcam.me.uk>
On Monday, June 12, 2017 09:23:22 PM Maciej W. Rozycki wrote:
> On Mon, 12 Jun 2017, John Baldwin wrote:
>
> > > Well, CP1.FIR is generally expected to hold non zero; in particular in
> > > legacy MIPS processors (before CP0.Config1.FP was defined) checking for a
> > > non-zero value in CP1.FIR (bits 15:8 specifically) was the recommended way
> > > to detect the presence of FPU hardware[1]. And from MIPSr1 on there have
> > > to be floating-point formats supported reported in CP1.FIR, with D and S
> > > being mandatory, so you'll see non-zero bits at least in their positions
> > > (the W bit was only added with MIPSr2).
> >
> > Ah, I had been going off of my (probably stale) copy of See Mips Run which
> > only talks about comparing FIR with 0. FreeBSD requires MIPSr3, so it should
> > always see a non-zero FIR then.
>
> FAOD MIPSr3 (as in MIPS32r3/MIPS64r3) or MIPS III?
Sorry, MIPS III only (so now I'm not certain if a non-zero FIR is guaranteed).
The only mips bits I have worked with myself are either qemu's malta targets
and a mips4000-ish 64-bit research CPU (all of which have FPUs).
--
John Baldwin
prev parent reply other threads:[~2017-06-13 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 16:58 John Baldwin
2017-06-05 20:27 ` Simon Marchi
2017-06-06 17:49 ` John Baldwin
2017-06-08 7:15 ` Maciej W. Rozycki
2017-06-12 18:47 ` John Baldwin
2017-06-12 20:23 ` Maciej W. Rozycki
2017-06-13 16:43 ` John Baldwin [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=2960345.dAXMQc0yB8@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@imgtec.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).