From: Jakub Jelinek <jakub@redhat.com>
To: FX <fxcoudert@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Harald Anlauf <anlauf@gmx.de>,
fortran@gcc.gnu.org, schwab@suse.de
Subject: Re: [PATCH] Fortran: make IEEE_CLASS recognize signaling NaNs
Date: Wed, 12 Jan 2022 11:34:19 +0100 [thread overview]
Message-ID: <20220112103419.GK2646553@tucnak> (raw)
In-Reply-To: <C1111E8E-6287-4593-A3E3-629068C06850@gmail.com>
On Wed, Jan 12, 2022 at 11:23:43AM +0100, FX via Gcc-patches wrote:
> I can confirm that I don’t see this failure on a Debian bullseye/sid (Linux 5.11.0-46, glibc 2.31-0ubuntu9.2) with a fresh bootstrap of master:
>
> $ grep signaling testsuite/gfortran/gfortran.sum
> PASS: gfortran.dg/ieee/signaling_1.f90 -O0 (test for excess errors)
> PASS: gfortran.dg/ieee/signaling_1.f90 -O0 execution test
> PASS: gfortran.dg/ieee/signaling_1.f90 -O1 (test for excess errors)
> PASS: gfortran.dg/ieee/signaling_1.f90 -O1 execution test
> PASS: gfortran.dg/ieee/signaling_1.f90 -O2 (test for excess errors)
> PASS: gfortran.dg/ieee/signaling_1.f90 -O2 execution test
> PASS: gfortran.dg/ieee/signaling_1.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors)
> PASS: gfortran.dg/ieee/signaling_1.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test
> PASS: gfortran.dg/ieee/signaling_1.f90 -O3 -g (test for excess errors)
> PASS: gfortran.dg/ieee/signaling_1.f90 -O3 -g execution test
> PASS: gfortran.dg/ieee/signaling_1.f90 -Os (test for excess errors)
> PASS: gfortran.dg/ieee/signaling_1.f90 -Os execution test
The error I was getting was:
/home/jakub/src/gcc/obj46/gcc/testsuite/gfortran2/../../gfortran -B/home/jakub/src/gcc/obj46/gcc/testsuite/gfortran2/../../ -B/home/jakub/src/gcc/obj46/x86_64-pc
-linux-gnu/./libgfortran/ /home/jakub/src/gcc/gcc/testsuite/gfortran.dg/ieee/signaling_1.f90 -fdiagnostics-plain-output -fdiagnostics-plain-output -O1 -fsignaling-nans /home/jakub/sr
c/gcc/gcc/testsuite/gfortran.dg/ieee/signaling_1_c.c -dumpbase -B/home/jakub/src/gcc/obj46/x86_64-pc-linux-gnu/./libgfortran/.libs -L/home/jakub/src/gcc/obj46/x86_64-pc-linux-gnu/./
libgfortran/.libs -L/home/jakub/src/gcc/obj46/x86_64-pc-linux-gnu/./libgfortran/.libs -L/home/jakub/src/gcc/obj46/x86_64-pc-linux-gnu/./libatomic/.libs -B/home/jakub/src/gcc/obj46/x8
6_64-pc-linux-gnu/./libquadmath/.libs -L/home/jakub/src/gcc/obj46/x86_64-pc-linux-gnu/./libquadmath/.libs -L/home/jakub/src/gcc/obj46/x86_64-pc-linux-gnu/./libquadmath/.libs -lm -o .
/signaling_1.exe
/home/jakub/src/gcc/gcc/testsuite/gfortran.dg/ieee/signaling_1.f90:8:20: Fatal Error: Cannot find an intrinsic module named 'ieee_arithmetic' at (1)
compilation terminated.
compiler exited with status 1
FAIL: gfortran.dg/ieee/signaling_1.f90 -O1 (test for excess errors)
Excess errors:
/home/jakub/src/gcc/gcc/testsuite/gfortran.dg/ieee/signaling_1.f90:8:20: Fatal Error: Cannot find an intrinsic module named 'ieee_arithmetic' at (1)
compilation terminated.
UNRESOLVED: gfortran.dg/ieee/signaling_1.f90 -O1 compilation failed to produce executable
And
-! { dg-options "-fsignaling-nans" }
+! { dg-additional-options "-fsignaling-nans" }
doesn't fix it, it changes the FAIL into:
cc1: warning: command-line option '-fintrinsic-modules-path /home/jakub/src/gcc/obj46/x86_64-pc-linux-gnu/./libgfortran/' is valid for Fortran but not for C
FAIL: gfortran.dg/ieee/signaling_1.f90 -O1 (test for excess errors)
Excess errors:
cc1: warning: command-line option '-fintrinsic-modules-path /home/jakub/src/gcc/obj46/x86_64-pc-linux-gnu/./libgfortran/' is valid for Fortran but not for C
We need -fintrinsic-modules-path option for the signalling_1.f90 compilation
but need to make sure it isn't used when the *.c file is compiled, so they
need to be compiled by separate compiler invocations probably.
Jakub
next prev parent reply other threads:[~2022-01-12 10:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 10:50 FX
2022-01-09 10:52 ` FX
2022-01-09 19:34 ` Mikael Morin
2022-01-10 12:04 ` FX
2022-01-11 22:01 ` Harald Anlauf
2022-01-11 22:01 ` Harald Anlauf
2022-01-11 22:04 ` FX
2022-01-11 22:11 ` Harald Anlauf
2022-01-11 22:11 ` Harald Anlauf
2022-01-11 22:32 ` FX
2022-01-12 10:23 ` FX
2022-01-12 10:34 ` Jakub Jelinek [this message]
2022-01-12 11:03 ` FX
2022-01-12 11:06 ` Jakub Jelinek
2022-01-12 11:55 ` 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=20220112103419.GK2646553@tucnak \
--to=jakub@redhat.com \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=schwab@suse.de \
/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).