From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: MIPS o32 ABI spec, $fp1 valid?
Date: Mon, 16 Jun 2003 18:51:00 -0000 [thread overview]
Message-ID: <20030616185054.GA30776@nevyn.them.org> (raw)
In-Reply-To: <3EEE0E2D.8050805@redhat.com>
On Mon, Jun 16, 2003 at 02:36:29PM -0400, Andrew Cagney wrote:
> Hello,
>
> KevinB and I were discussing MIPS cleanups for better handling things
> like o32 ABI. One question was can the o32 ABI use odd floating point
> registers? The MIPS certainly has them, and instructions can certainly
> access them. However, according to the o32 ABI, can they be used?
>
> (alternativly, does anyone have a MIPS o32 ABI spec, and even the
> original ABI spec that went with the MIPS 1).
Hum, here's what the SysV ABI Supplement for MIPS (1996?) has to say:
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).
Which is actually pretty ambiguous, but GCC goes out of its way not to
put floats in odd-numbered FP registers (unless -msingle-float), so I'm
guessing that the ABI spec says they may _not_ be used.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-06-16 18:51 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 [this message]
[not found] ` <mailpost.1055789524.339@news-sj1-1>
2003-06-17 5:34 ` cgd
2003-06-17 13:53 ` Andrew Cagney
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=20030616185054.GA30776@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.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