From: Piotr Kubaj <pkubaj@anongoth.pl>
To: FX <fxcoudert@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Fortran List <fortran@gcc.gnu.org>,
segher@kernel.crashing.org
Subject: Re: [PATCH] fortran: use fpu-glibc on powerpc*-unknown-freebsd
Date: Sat, 30 Apr 2022 20:28:31 +0200 [thread overview]
Message-ID: <Ym1/zyOTIvoKH5sY@KGPE-D16> (raw)
In-Reply-To: <4E88DC70-EF18-47AC-991B-5161AE37EBE1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 441 bytes --]
On 22-04-28 20:55:08, FX wrote:
> > Given that 12 has been branched off, is it OK now to commit this patch?
>
> How does the patch affect the results of “make check-gfortran”? How many tests that failed or were unsupported pass?
Actually, test results don't change at all. However, software that otherwise fails to build with "Cannot find an intrinsic module named 'ieee_arithmetic'", now builds successfully.
>
> FX
--
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-04-30 18:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 15:30 FX
2022-04-13 14:56 ` Piotr Kubaj
2022-04-13 15:27 ` FX
2022-04-14 0:49 ` Piotr Kubaj
2022-04-14 7:05 ` FX
2022-04-14 14:09 ` Piotr Kubaj
2022-04-28 17:09 ` Piotr Kubaj
2022-04-28 18:55 ` FX
2022-04-30 18:28 ` Piotr Kubaj [this message]
2022-04-30 19:17 ` 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=Ym1/zyOTIvoKH5sY@KGPE-D16 \
--to=pkubaj@anongoth.pl \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).