From: Joseph Myers <joseph@codesourcery.com>
To: Michael Meissner <meissner@linux.ibm.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
Peter Bergner <bergner@linux.ibm.com>, <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH 0/5] IEEE 128-bit built-in overload support.
Date: Thu, 11 Aug 2022 20:44:17 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2208112043400.90368@digraph.polyomino.org.uk> (raw)
In-Reply-To: <YvVgIId0UAPaORXB@toto.the-meissners.org>
On Thu, 11 Aug 2022, Michael Meissner via Gcc-patches wrote:
> In looking at it, I now believe that the type for _Float128 and __float128
> should always be the same within the compiler. Whether we would continue to
> use the same type for long double and _Float128/__float128 remains to be seen.
long double and _Float128 must always be different types; that's how it's
defined in C23.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-08-11 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 4:43 Michael Meissner
2022-07-28 4:47 ` [PATCH 1/5] " Michael Meissner
2022-07-28 4:48 ` [PATCH 2/5] Support IEEE 128-bit overload round_to_odd built-in functions Michael Meissner
2022-07-28 4:50 ` [PATCH 3/5] Support IEEE 128-bit overload comparison " Michael Meissner
2022-07-28 4:52 ` [PATCH 4/5] Support IEEE 128-bit overload extract and insert " Michael Meissner
2022-07-28 4:54 ` [PATCH 5/5] Support IEEE 128-bit overload test data " Michael Meissner
2022-08-03 17:58 ` Ping: [PATCH 0/5] IEEE 128-bit built-in overload support Michael Meissner
2022-08-05 18:19 ` Segher Boessenkool
2022-08-10 6:23 ` Michael Meissner
2022-08-10 17:03 ` Segher Boessenkool
2022-08-11 20:01 ` Michael Meissner
2022-08-11 20:44 ` Joseph Myers [this message]
2022-08-16 18:07 ` Jakub Jelinek
2022-08-16 18:55 ` Segher Boessenkool
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.2208112043400.90368@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.ibm.com \
--cc=segher@kernel.crashing.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).