From: Thomas Koenig <tkoenig@netcologne.de>
To: FX <fxcoudert@gmail.com>, fortran@gcc.gnu.org
Cc: Iain Sandoe <iain@sandoe.co.uk>, gcc-patches@gcc.gnu.org
Subject: Re: [patch, Fortran] Make REAL(KIND=16) detection more robust
Date: Sun, 19 Dec 2021 22:02:15 +0100 [thread overview]
Message-ID: <2bd8fb54-462c-228a-b002-35f7cf4d080d@netcologne.de> (raw)
In-Reply-To: <8CA66B79-11B1-40B2-B361-F8835EF4DF1B@gmail.com>
Hi FX,
I am not sure the logic is correct for POWER (old style) where we have
a 16-byte long double made up from two 8-byte doubles, which is not
__float128 (IFmode), see
https://gcc.gnu.org/pipermail/fortran/2021-November/056912.html
I have a proposal: Since I am currently trying to unravel this
on the power-ieee128 branch, I would like to take this on,
if that is fine with you.
Best regards
Thomas
next prev parent reply other threads:[~2021-12-19 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 14:11 FX
2021-12-15 8:59 ` FX
2021-12-19 21:02 ` Thomas Koenig [this message]
2021-12-19 23:42 ` FX
2021-12-20 12:12 ` Thomas Koenig
2021-12-22 11:51 ` FX
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=2bd8fb54-462c-228a-b002-35f7cf4d080d@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
/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).