public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@science.uva.nl>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: [rfc] Add some more floatformat types ....
Date: Thu, 16 Aug 2001 16:55:00 -0000	[thread overview]
Message-ID: <s3iu1z7lfy2.fsf@soliton.wins.uva.nl> (raw)
In-Reply-To: <3B7C1287.9080906@cygnus.com>

Andrew Cagney <ac131313@cygnus.com> writes:

> > The attached adds the floatformats:
> > 
> > floatformat_i387_ext80;
> > floatformat_i387_ext96;
> > 
> >     Explicitly sized x86 float formats.
> > 
> >     Depending on where/how it is stored,
> >     an i386 extended could use 80 (10 bytes)
> >     or 96 (12 bytes).

Andrew, I thought I (implicitly) raised some objections to this
change.  See

   http://sources.redhat.com/ml/gdb/2001-07/msg00401.html

To clarify things a bit: The ISA (that stands for Istruction Set
Architecture doesn't it) defines a single 80-bit extended floating
point format.  On top of that floating point format most ABI's build a
a 96-bit extended floating point type (e.g. GCC's `long double').  I'd
like GDB to somehow maintain this concept, by *not* introducing the
floatformat_i387_ext80 and floatformat_i387_ext96 types you propose.
Instead we should make the distinction at the builtin_type_* level.
By making the 80-bit and 96-bit builtin_type_* variants share the same
underlying floatformat_* variable, we can easiliy check whether two
floating point formats on the ABI level share the same encoding on the
ISA level.

Something similar might hold for IA-64.

The other two fixes seem obvious to me.

Mark

  reply	other threads:[~2001-08-16 16:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-11 22:46 Andrew Cagney
2001-08-16 11:36 ` Andrew Cagney
2001-08-16 16:55   ` Mark Kettenis [this message]
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=s3iu1z7lfy2.fsf@soliton.wins.uva.nl \
    --to=kettenis@science.uva.nl \
    --cc=ac131313@cygnus.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).