From: Jakub Jelinek <jakub@redhat.com>
To: Mikael Morin <morin-mikael@orange.fr>,
fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org,
Harald Anlauf <anlauf@gmx.de>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: [PATCH] fortran, libgfortran, v3: Avoid using libquadmath for glibc 2.26+
Date: Tue, 28 Jun 2022 09:01:43 +0200 [thread overview]
Message-ID: <YrqnV5a75Df3I+aV@tucnak> (raw)
In-Reply-To: <YrmxCTxa3L5ZhNmy@tucnak>
On Mon, Jun 27, 2022 at 03:30:49PM +0200, Jakub Jelinek via Gcc-patches wrote:
> Ok, here is an updated patch that uses _Float128/_Complex _Float128 for all
> of GFC_REAL_{16,17}_IS_FLOAT128, but still uses q/Q suffixes on literal
> constants etc. when using libquadmath and f128/F128 otherwise.
> This patch also includes the incremental powerpc64le fixes.
>
> Ok if it passes testing?
Bootstrapped/regtested successfully on x86_64-linux and i686-linux with
glibc 2.35 (libquadmath not used), powerpc64le-linux with glibc 2.17
(libquadmath used for -mabi=ieeelongdouble support), powerpc64le-linux
with 2.28 (libquadmath not used), powerpc64-linux with glibc 2.17
(libquadmath not used, real(kind=16) only long double IBM double double).
Jakub
next prev parent reply other threads:[~2022-06-28 7:01 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 [this message]
2022-06-28 8:35 ` Tobias Burnus
2022-06-28 10:57 ` Jakub Jelinek
2022-06-27 20:54 ` [PATCH] fortran, libgfortran, v2: " Joseph Myers
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=YrqnV5a75Df3I+aV@tucnak \
--to=jakub@redhat.com \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).