From: cgd@broadcom.com
To: kevinb@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] MIPS: Consolidate printing of floating point registers
Date: Sat, 05 Apr 2003 20:03:00 -0000 [thread overview]
Message-ID: <yov5r88giuev.fsf@broadcom.com> (raw)
In-Reply-To: kevinb@redhat.com's message of "Sat, 5 Apr 2003 00:09:22 +0000 (UTC)"
At Sat, 5 Apr 2003 00:09:22 +0000 (UTC), "Kevin Buettner" wrote:
> Also, for some MIPS parts, floating point registers may contain values
> which are not really floating point numbers, so a hex display of these
> registers is useful. (Thanks to Chris Demetriou for telling me about
> this.)
To explain further to casual but interested readers:
(a) it's possible to load/store random values thru the FP regs.
(b) since the r3000 AFAIK, it's been possible to convert FP values to
integer values in FP regs. (cvt.w.<fmt>) Starting with MIPS III (r4k)
you an also do this for 64-bit intever values, using cvt.d.<fmt>.
(c) MIPS V adds other formats, e.g. "Paired Single", in which two FP
single values are in a single FP register. (It's v2sf in gcc
modespeak. 8-)
printing out FP values as singles & doubles is often the right thing
(since usually a given FP reg will contain one or the other) but, to
look at it another way, if you do that then between 0 and 1 of the 2
values you've printed are actually correct. Printing the hex value as
well is fairly horrible, but at least you're given at least one value
that's correct. 8-)
chris
next prev parent reply other threads:[~2003-04-05 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-05 0:09 Kevin Buettner
2003-04-05 19:10 ` Andrew Cagney
[not found] ` <mailpost.1049501362.14712@news-sj1-1>
2003-04-05 20:03 ` cgd [this message]
2003-04-07 18:39 ` Kevin Buettner
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=yov5r88giuev.fsf@broadcom.com \
--to=cgd@broadcom.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.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