https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
--- Comment #7 from kargl at gcc dot gnu.org --- (In reply to Peter Bergner from comment #5) > Hmm, the test case is explicitly adding the options > -ffpe-trap=overflow,invalid, so is this a test case error? We tell it to > trap on invalid fp operations which we force it to do when generating the > signaling nan value. Removing the above option allows the reduced test case > to not die. > > bergner@pike:~/gcc/BUGS/PR88678$ gfortran -ffpe-trap=invalid -static bug.f90 > bergner@pike:~/gcc/BUGS/PR88678$ ./a.out > > Program received signal SIGFPE: Floating-point exception - erroneous > arithmetic operation. > > Backtrace for this error: > #0 0x10001b1b > Floating point exception > bergner@pike:~/gcc/BUGS/PR88678$ gfortran -static bug.f90 > bergner@pike:~/gcc/BUGS/PR88678$ ./a.out > bergner@pike:~/gcc/BUGS/PR88678$ The testcase is correct. It appears that powerpc is claiming that it has the ability for a user to manipulate the floating-point exception handling, but it appears something is going sideways. This is why all ieee testcases are now failing only on powerpc64. See my comment #3. I assume that fpu-target.h is pulling in libgfortran/config/fpu-glibc.h, and either that file is broken or as your backtrace in comment #2 suggests sysdeps/powerpc/fpu/feenablxcpt.c is broken.
