From: Jim Wilson <jimw@sifive.com>
To: Dennis Clarke <dclarke@blastwave.org>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: making double type default to 80 or 128 bytes
Date: Mon, 10 Aug 2020 16:37:17 -0700 [thread overview]
Message-ID: <CAFyWVab4+60RWk6iD6LYRqTdnBBw95Mz-FjTMg4j5_Rd2-WsTQ@mail.gmail.com> (raw)
In-Reply-To: <9a66e245-61cf-9eb2-f4f5-3fc7d10d9ff8@blastwave.org>
On Fri, Aug 7, 2020 at 9:00 AM Dennis Clarke via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
> There is no such thng as an 80 byte double. The standards state that we
> shall use floating point types which are of specific bit widths and all
> of those are perfectly aligned on perfect power of two bit widths. These
> range from 16 bits to 256 bit width. To date I have not seen hardware
> which natively supports the 256-bit floating point type. The IBM POWER9
> processor as well as the RISC-V and Fujitsu SPARC provide hardware for
> the 128-bit width and they seem to work very well indeed. The 80-bit
> thing to which you refer is a hack put in place by the intel/x86 world
> simply because the hardware can not properly handle anything larger. It
> should not exist at all in if we use the floating point standards.
The IEEE FP standard defines some basic formats which have fixed
bit-widths, and extended formats which have implementation defined bit
widths. The 80-bit x86 format meets the definition of extended
binary64 in the 2008 standard, and extended double in the 1985
standard. Likewise the similar 96 bit (with 16-bits of zero padding)
format used on 68k systems. Nowadays though, I think most people
would rather have a proper 128-bit long double than an 80/96-bit
extended double. But there is nothing hackish about the 80/96 bit
extended doubles on x86/68k. They have just outlived their
usefulness.
Jim
next prev parent reply other threads:[~2020-08-10 23:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 14:59 dave
2020-08-07 15:38 ` Dallman, John
2020-08-07 15:59 ` Dennis Clarke
2020-08-10 23:37 ` Jim Wilson [this message]
2020-08-07 18:23 ` Jonathan Wakely
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=CAFyWVab4+60RWk6iD6LYRqTdnBBw95Mz-FjTMg4j5_Rd2-WsTQ@mail.gmail.com \
--to=jimw@sifive.com \
--cc=dclarke@blastwave.org \
--cc=gcc-help@gcc.gnu.org \
/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).