From: Kevin Buettner <kevinb@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>,
Mark Kettenis <kettenis@wins.uva.nl>,
Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc] Add some more floatformat types ....
Date: Fri, 17 Aug 2001 09:40:00 -0000 [thread overview]
Message-ID: <1010817163956.ZM4083@ocotillo.lan> (raw)
In-Reply-To: <3B7D4280.8010005@cygnus.com>
On Aug 17, 12:12pm, Andrew Cagney wrote:
> > The IA-64, for instance, has an 82 bit floating-point register. That
> > register is always represented in memory as 128 bits.
> Consequently, my
> > proposal includes ia64_ext128 and not ia64_ext82.
> >
> > So we only need a single floatformat_ia64_ext. Why not keep the
> > floatformat_ia64_ext that we already have in ia64-tdep.c and move it
> > to ../libiberty/floatformat.c?
>
> Dam! You spotted my cunning plan :-) That is one of the next steps.
> In the light of the exchange above, a double check on this one is in order.
>
> Kevin, am I correct in saying that the ia64 reads/writes 16 bytes when
> loading/storing an ia64_ext?
Yes. But I'd rephrase it as... The IA-64 reads/writes 16 bytes when
loading/storing the 82-bit floating point register format.
The fly in the ointment is that the IA-64 also has a quad precision
real type whose width is 128 bits (1 bit sign, 15 bit exponent,
112 bit significand).
> Mark, this meaning that the ia64_ext should have a size of 128 and not
> 82 as it currently does in ia64-tdep.c?
In order to avoid confusion, I think it might be better for the name
to reflect the actual number of bits used in the memory container as
well as the width of the memory container. Maybe something along the
lines of ia64_reg82_mem128? Perhaps something similar could also be
done of x86?
next prev parent reply other threads:[~2001-08-17 9:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B76164B.9060908@cygnus.com>
2001-08-16 11:36 ` Andrew Cagney
2001-08-16 16:55 ` Mark Kettenis
2001-08-16 20:10 ` Andrew Cagney
2001-08-17 6:08 ` Mark Kettenis
2001-08-17 9:13 ` Andrew Cagney
2001-08-17 9:40 ` Kevin Buettner [this message]
2001-08-17 10:12 ` Andrew Cagney
2001-08-17 11:12 ` Kevin Buettner
2001-08-17 12:19 ` Mark Kettenis
2001-08-17 12:34 ` Andrew Cagney
2001-08-17 12:51 ` Kevin Buettner
2001-08-18 12:04 ` Andrew Cagney
2001-08-17 12:30 ` Andrew Cagney
2001-08-17 12:32 ` Mark Kettenis
2001-08-21 6:41 ` Fernando Nasser
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=1010817163956.ZM4083@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@wins.uva.nl \
/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