From: Mark Kettenis <kettenis@wins.uva.nl>
To: kevinb@cygnus.com
Cc: ac131313@cygnus.com, kevinb@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [rfc] Add some more floatformat types ....
Date: Fri, 17 Aug 2001 12:19:00 -0000 [thread overview]
Message-ID: <200108171919.f7HJJWF00447@delius.kettenis.local> (raw)
In-Reply-To: <1010817181153.ZM4294@ocotillo.lan>
Date: Fri, 17 Aug 2001 11:11:53 -0700
From: Kevin Buettner <kevinb@cygnus.com>
[snip]
Anyway, my objection to using ``ia64_ext'' for the 82-bit register
type stems from the fact that this name would probably be more
appropriate for the 80-bit double-extended type. Especially since
this is the convention already used for x86. How 'bout this instead?
ia64_ext - 80-bit double-extended
ia64_reg - 82-bit fp register
ia64_quad - 128-bit quad-precision
I was going to propose exactly the same :-). FYI Andrew, the ia64_ext
type is stored in 10 bytes of memory, the ia64_reg type is stored in
16 bytes of memory and ia64_quad is also stored in 16 bytes of memory.
It seems that ia64_ext would be identical to i387_ext, so we could
simply
#define floatformat_ia64_ext floatformat_i387_ext
in floatformat.h.
Mark
next prev parent reply other threads:[~2001-08-17 12:19 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
2001-08-17 10:12 ` Andrew Cagney
2001-08-17 11:12 ` Kevin Buettner
2001-08-17 12:19 ` Mark Kettenis [this message]
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=200108171919.f7HJJWF00447@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@cygnus.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