Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@jive.nl>
To: brobecker@gnat.com
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [RFA/mips] 128-bit long doubles for N32/N64
Date: Tue, 03 Aug 2004 07:27:00 -0000	[thread overview]
Message-ID: <200408030726.i737Q9uw013721@juw15.nfra.nl> (raw)
In-Reply-To: <20040803043906.GZ32638@gnat.com> (message from Joel Brobecker on Mon, 2 Aug 2004 21:39:06 -0700)

   Date: Mon, 2 Aug 2004 21:39:06 -0700
   From: Joel Brobecker <brobecker@gnat.com>

   > >Then let's let the fortran developpers fix it :-).
   > 
   > Or the Ada developers :-)

   Honestly, I think we're letting the best be the enemy of good.
   We have the choice between printing an approximation of a float,
   or printing nothing at all. Some users will be satisfied with
   the approximation. I will be. Why penalize these users?

I agree.

   I am ok with documenting this approximation in the GDB manual.
   If whoever wants to fix this later, then fine. But in the meantime,
   I think something is better than nothing.

Folks, Please realize that in practice, printing an approximation is
the best we can do anyway.  Unless we've got a native GDB and we've
properly set the host's floatformat in configure.host.  And in that
case the actual description shouldn't really matter; just that it
matches the description of the target floatformat.  So ...

   > >I vote for setting the format to ieee-double with a comment.
   > 
   > That would also be wrong.
   > 
   > Closer would be a new 128bit irix floatformat that knew how to unpack 
   > the first 64-bits.

   Indeed, maybe it would be cleaner to create a new irix-specific
   128bit floatformat that only uses the bits in the high part (basically,
   it would be a copy of the ieee_big with the size set to 128bits,
   or something like that, right?).

.. this seems a perfectly acceptable solution to me.  It'd avoid us
to really lie about the floating-point format, even though we're not
telling the complete truth.

Mark


  reply	other threads:[~2004-08-03  7:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22 15:44 Joel Brobecker
2004-07-26 22:19 ` Andrew Cagney
2004-07-26 22:45   ` Joel Brobecker
2004-07-27 15:37     ` Andrew Cagney
2004-08-02  1:15       ` Joel Brobecker
2004-08-02  1:43         ` Michael Chastain
2004-08-02 18:31         ` Andrew Cagney
2004-08-03  1:13           ` Joel Brobecker
2004-08-03  1:59             ` Andrew Cagney
2004-08-03  4:39               ` Joel Brobecker
2004-08-03  7:27                 ` Mark Kettenis [this message]
2004-08-03 13:31                   ` Paul Koning
2004-08-04  4:00                     ` Alexandre Oliva
2004-08-04  7:19                     ` Mark Kettenis
2004-08-03  3:19             ` Michael Chastain

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=200408030726.i737Q9uw013721@juw15.nfra.nl \
    --to=kettenis@jive.nl \
    --cc=brobecker@gnat.com \
    --cc=cagney@gnu.org \
    --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