From: Paul Koning <pkoning@equallogic.com>
To: kettenis@jive.nl
Cc: brobecker@gnat.com, cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [RFA/mips] 128-bit long doubles for N32/N64
Date: Tue, 03 Aug 2004 13:31:00 -0000 [thread overview]
Message-ID: <16655.37815.285599.668840@gargle.gargle.HOWL> (raw)
In-Reply-To: <200408030726.i737Q9uw013721@juw15.nfra.nl>
>>>>> "Mark" == Mark Kettenis <kettenis@jive.nl> writes:
>> 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.
Mark> Folks, Please realize that in practice, printing an
Mark> approximation is the best we can do anyway.
I'm not sure the present case warrants the effort, but I don't think
that's true. You could lift the gcc code in real.c, which has
conversions between target format and an oversized internal format.
With that you would be able to process 128 bit floats correctly on any
host.
Then again, I'm not sure why MIPS N32 is defined to have 128 bit
floats in the first place. It seems rather silly considering that
there isn't any such data type in the machine instruction set.
paul
next prev parent reply other threads:[~2004-08-03 13:31 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
2004-08-03 13:31 ` Paul Koning [this message]
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=16655.37815.285599.668840@gargle.gargle.HOWL \
--to=pkoning@equallogic.com \
--cc=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@jive.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