From: Andrew Cagney <ac131313@redhat.com>
To: cgd@broadcom.com
Cc: drow@mvista.com, gdb@sources.redhat.com
Subject: Re: MIPS o32 ABI spec, $fp1 valid?
Date: Tue, 17 Jun 2003 13:53:00 -0000 [thread overview]
Message-ID: <3EEF1D51.7000300@redhat.com> (raw)
In-Reply-To: <yov5u1ape07k.fsf@ldt-sj3-010.sj.broadcom.com>
Now we're getting somewhere :-) Next question.
Does the o32 ABI specify how to spill a loating point register (a spill
is different to a double store of a parameter as a spilt register is
recovered by the unwind code. mdebug might, for instance, specify
something.
Andrew
>> Co-processor 1 adds 32 32-bit floating-point general registers and a
>> 32-bit control/status register. Each even/odd pair of the 32
>> floating-point general registers can be used as either a 32-bit
>> single-precision floating-point register or as a 64-bit
>> double-precision floating-point register. For single-precision values,
>> the even-numbered floating-point register holds the value. For
>> double-precision values, the even-numbered floating-point register
>> holds the least significant 32 bits of the value and the odd-numbered
>> floating-point register holds the most significant 32 bits of the
>> value. This is always true, regardless of the byte ordering conventions
>> in use ( big endian or little endian).
>
>
> FYI, the above agrees with my reading of Kane (see
> http://sources.redhat.com/ml/gdb-patches/2003-06/msg00555.html ).
>
> The ISBN is 0135847494. it can be found used in lots of places for
> approx $10. I paid more for mine 10+ years ago. 8-)
>
>
>
>> Which is actually pretty ambiguous,
>
>
> not really at all: "Each even/odd pair... as either _a_ 32-bit ..."
> etc.
>
> Kane makes clear:
>
> In the following pages, the notation <i>FGR</i> refers to the
> FPA's general register 0 through 31, and <i>FPR</i> refers ot
> the FPA's floating-point registers (FPR 0 through 30) which
> are formed by concatenation of FGR's[sic] (as described in
> <b>Chapter 6</b>).
>
> Chapter 6 really makes quite clear that there are 16 FGRs.
>
>
>
> cgd
>
>
next prev parent reply other threads:[~2003-06-17 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 18:36 Andrew Cagney
2003-06-16 18:51 ` Daniel Jacobowitz
[not found] ` <mailpost.1055789524.339@news-sj1-1>
2003-06-17 5:34 ` cgd
2003-06-17 13:53 ` Andrew Cagney [this message]
2003-06-17 19:51 David Anderson
2003-06-17 20:13 David Anderson
2003-06-18 16:12 ` Andrew Cagney
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=3EEF1D51.7000300@redhat.com \
--to=ac131313@redhat.com \
--cc=cgd@broadcom.com \
--cc=drow@mvista.com \
--cc=gdb@sources.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