From: Joseph Myers <joseph@codesourcery.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Sjoerd Meijer <Sjoerd.Meijer@arm.com>,
Kito Cheng <kito.cheng@gmail.com>, GCC <gcc@gcc.gnu.org>
Subject: Re: IEEE Interchange floating point and extended floating point for C++
Date: Fri, 12 Mar 2021 21:55:14 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2103122153050.939551@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAH6eHdT52XY3yfh9aNpYkKduJw57VN-U_Z-JSp9abBYAmBQFSQ@mail.gmail.com>
On Fri, 12 Mar 2021, Jonathan Wakely via Gcc wrote:
> I see less value in adding additional distinct types that don't add
> anything you can't already do. _Float16 gives you access to an entirely new
> data type. _Float32 just complicates overloading of it's a new type with
So would you then support _Float128, and the corresponding f128/F128
literal suffixes, in C++, as a "more standard" version of __float128, in
the case where it has a different format from long double (e.g. x86_64)
but not when it has the same format as long double?
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-03-12 21:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 9:07 Kito Cheng
2021-03-11 12:56 ` Jonathan Wakely
2021-03-11 14:02 ` Gabriel Ravier
2021-03-11 15:14 ` Jonathan Wakely
2021-03-11 15:14 ` Jonathan Wakely
2021-03-12 6:50 ` Kito Cheng
2021-03-11 14:26 ` Joseph Myers
2021-03-12 7:17 ` Kito Cheng
2021-03-12 9:27 ` Jonathan Wakely
2021-03-12 11:42 ` Sjoerd Meijer
2021-03-12 12:31 ` Jonathan Wakely
2021-03-12 17:49 ` Joseph Myers
2021-03-12 18:14 ` Joseph Myers
2021-03-12 20:53 ` Jonathan Wakely
2021-03-12 21:55 ` Joseph Myers [this message]
2021-03-12 22:03 ` Jonathan Wakely
2021-03-15 10:16 ` Sjoerd Meijer
2021-03-15 10:20 ` 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=alpine.DEB.2.22.394.2103122153050.939551@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Sjoerd.Meijer@arm.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=kito.cheng@gmail.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).