From: Joseph Myers <joseph@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Mikael Morin <morin-mikael@orange.fr>, <fortran@gcc.gnu.org>,
<gcc-patches@gcc.gnu.org>, Harald Anlauf <anlauf@gmx.de>
Subject: Re: [PATCH] fortran, libgfortran, v2: Avoid using libquadmath for glibc 2.26+
Date: Mon, 27 Jun 2022 20:54:32 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2206272049320.211537@digraph.polyomino.org.uk> (raw)
In-Reply-To: <YrliJXK79C/R2TSo@tucnak>
On Mon, 27 Jun 2022, Jakub Jelinek via Gcc-patches wrote:
> On Sun, Jun 26, 2022 at 08:45:28PM +0200, Mikael Morin wrote:
> > I don’t like the _Float128 vs __float128 business, it’s confusing.
> > And accordinog to https://gcc.gnu.org/onlinedocs/gcc/Floating-Types.html
> > they seem to be basically the same thing, so it’s also redundant.
>
> I thought __float128 and _Float128 are distinct and incompatible in the FEs
> and equivalent in middle-end and back-end, but apparently they are
> considered equivalent even for _Generic.
Yes, when both are supported, they are the same type. The main
differences (not relevant for this patch, I think) are:
* _Float128 is supported on systems where long double has the IEEE
binary128 format (as a distinct type from long double even when they have
the same format); __float128 generally isn't supported on such systems.
* __float128 is supported in C++, _Float128 isn't (though we've discussed
adding support for _FloatN type names and corresponding fN constant
suffixes in C++; see the thread on the gcc list in March 2021).
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2022-06-27 20:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 12:04 [PATCH] fortran, libgfortran: " Jakub Jelinek
2022-06-23 20:49 ` Harald Anlauf
2022-06-23 21:17 ` Jakub Jelinek
2022-06-24 10:29 ` [PATCH] fortran, libgfortran, v2: " Jakub Jelinek
2022-06-24 21:06 ` Harald Anlauf
2022-06-26 18:45 ` Mikael Morin
2022-06-27 7:54 ` Jakub Jelinek
2022-06-27 11:56 ` Mikael Morin
2022-06-27 13:30 ` [PATCH] fortran, libgfortran, v3: " Jakub Jelinek
2022-06-28 7:01 ` Jakub Jelinek
2022-06-28 8:35 ` Tobias Burnus
2022-06-28 10:57 ` Jakub Jelinek
2022-06-27 20:54 ` Joseph Myers [this message]
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.2206272049320.211537@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=morin-mikael@orange.fr \
/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).