public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: FX <fxcoudert@gmail.com>
To: Piotr Kubaj <pkubaj@anongoth.pl>
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 21:17:31 +0200	[thread overview]
Message-ID: <9F15617C-D36F-4EAD-BD2F-297CD9118E02@gmail.com> (raw)
In-Reply-To: <Ym1/zyOTIvoKH5sY@KGPE-D16>

[-- Attachment #1: Type: text/plain, Size: 647 bytes --]

> 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.

Test results should definitely change, we’d need to see a before/after list (same build, same revision, without and with patch applied) to know. Run “make check-gfortran”.

All tests in gcc/testsuite/gfortran.dg/ieee/ should be running and running fine (i.e., PASS). You can also grep for “ieee” in the gcc/testsuite/gfortran.sum file created after “make check-gfortran” is run, and report both here. This will help investigate.

Thanks,
FX

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-04-30 19:17 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
2022-04-30 19:17                 ` FX [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=9F15617C-D36F-4EAD-BD2F-297CD9118E02@gmail.com \
    --to=fxcoudert@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=pkubaj@anongoth.pl \
    --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).