Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>, Kevin Buettner <kevinb@cygnus.com>
Cc: Mark Kettenis <kettenis@wins.uva.nl>, gdb-patches@sources.redhat.com
Subject: Re: [rfc] Add some more floatformat types ....
Date: Fri, 17 Aug 2001 11:12:00 -0000	[thread overview]
Message-ID: <1010817181153.ZM4294@ocotillo.lan> (raw)
In-Reply-To: <3B7D507D.4010801@cygnus.com>

On Aug 17,  1:12pm, Andrew Cagney wrote:

> > 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).
> 
> Ulgh!  So we now need two IA-64 floating point types, any suggestion for 
> a name? Does:
> 
> 	ia64_ext
> 	ia64_quad
> 
> look ok (and please no one look at the VAX :-).

Well, actually, there are a total of seven data types that the IA-64
supports.  (However, two of them are integer types.) From section 5.1
of the Intel IA-64 Architecture Software Developer's Manual; Volume 1: 
IA-64 Application Architecture:

    Six data types are supported directly:  single, double,
    double-extended real (IEEE real types); 64-bit signed integer,
    64-bit unsigned integer, and the 82-bit floating point register
    format.  A "Parallel FP" format where a pair of IEEE single
    precision values occupy a floating point registers significand is
    also supported.  A seventh data type, IEEE-style quad-precision,
    is supported in software routines.  A future architecture
    extension may include additional support for the quad-precision
    real type.

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

Online documentation on the IA-64 floating point formats may be found at:

    http://devresource.hp.com/devresource/Docs/Refs/IA64ISA/fp_program4.html 

Roughly the same material may also be found in chapter 5 of the
following PDF file:

    ftp://download.intel.com/design/IA-64/Downloads/24531702s.pdf

Kevin


  reply	other threads:[~2001-08-17 11:12 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 [this message]
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=1010817181153.ZM4294@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