From: cgd@broadcom.com
To: drow@false.org
Cc: "Joel Brobecker" <brobecker@gnat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] mips-irix SEGV: long doubles are 128 bits long on IRIX
Date: Thu, 22 Jul 2004 01:19:00 -0000 [thread overview]
Message-ID: <yov5y8lc3kk9.fsf@ldt-sj3-010.sj.broadcom.com> (raw)
In-Reply-To: <mailpost.1090457371.25819@news-sj1-1>
At Thu, 22 Jul 2004 00:49:31 +0000 (UTC), "Daniel Jacobowitz" wrote:
> I don't think NetBSD even supports mips64. Not in GCC HEAD, at least.
NetBSD doesn't support n32 or n64, or have any real support for
'mips64' at all, at this time (AFAIK).
> According to GCC long double is 128-bit for all n64 and n32 targets.
Note that the actual 'long double' format is *different* between
Linux and IRIX, AFAIK.
On Linux (w/ glibc), it's 128 bits in the typical IEEE format -- I
don't recall what the exact terminology or specification for 128-bit
IEEE-style value is, tho. (like normal double, but wider mantissa and
wider exponent.)
On IRIX, if i recall correctly, 'long double' is implemented as a
*pair of doubles*, which allows one to get somewhat-extended
precision, but doesn't allow the complete range of 128-bit IEEE-style.
(I imagine the benefit is, you can do at least some of the 'long
double' ops w/ 'double' FP ops in HW. So, better speed... maybe.)
cgd
next prev parent reply other threads:[~2004-07-22 1:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 21:25 Joel Brobecker
2004-07-21 21:30 ` Daniel Jacobowitz
2004-07-21 23:33 ` Joel Brobecker
2004-07-22 0:40 ` Daniel Jacobowitz
2004-07-22 0:46 ` Joel Brobecker
2004-07-22 0:49 ` Daniel Jacobowitz
[not found] ` <mailpost.1090457371.25819@news-sj1-1>
2004-07-22 1:19 ` cgd [this message]
2004-07-22 1:27 ` Daniel Jacobowitz
2004-07-22 2:09 ` Joel Brobecker
2004-07-22 2:21 ` Daniel Jacobowitz
2004-07-22 2:34 ` Joel Brobecker
2004-07-22 2:36 ` Daniel Jacobowitz
2004-07-23 17:00 David Anderson
2004-07-26 22:18 ` Andrew Cagney
[not found] ` <mailpost.1090880398.10041@news-sj1-1>
2004-07-26 22:41 ` cgd
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=yov5y8lc3kk9.fsf@ldt-sj3-010.sj.broadcom.com \
--to=cgd@broadcom.com \
--cc=brobecker@gnat.com \
--cc=drow@false.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