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
