Closed pums974 closed 3 weeks ago
This is due to moving our floating-point type introspection to a run-time check instead of a compile-time check (to better support cross-compiling). After the 1.14.3 release, we added code that disables floating-point exceptions while we introspect the types.
Can you check if this behavior persists in the current develop branch?
We've hit the same problem with our Fortran code when exploring upgrading to 1.14 from 1.12. With Intel ifort and ifx "-init=snan" causes the problem as the OP reported. But more generally it happens if floating point exception trapping is enabled with any Fortran compiler: via the -fpe0
ifort and ifx flag, or the -ieee=nonstd
option with the NAG compiler (which is the default!), or the -ffpe-trap=invalid
gfortran flag. We've tentatively had to disable FP exception trapping, which makes us very uncomfortable. I hope this is a (very) temporary issue with HDF5.
We've hit the same problem with our Fortran code when exploring upgrading to 1.14 from 1.12. With Intel ifort and ifx "-init=snan" causes the problem as the OP reported. But more generally it happens if floating point exception trapping is enabled with any Fortran compiler: via the
-fpe0
ifort and ifx flag, or the-ieee=nonstd
option with the NAG compiler (which is the default!), or the-ffpe-trap=invalid
gfortran flag. We've tentatively had to disable FP exception trapping, which makes us very uncomfortable. I hope this is a (very) temporary issue with HDF5.
Have you tried the latest develop or hdf5_1_14 branches? Those should have a fix for this.
Is this fixed w/ 1.14.4?
I tested with the 1.14.4-2 tar file and it appears to be fixed. I'm not sure why the 1.14.5 milestone was mentioned.
Compiling a user fortran code with ifort or ifx using the debug option "-init=snan" is triggering a segmentation fault at runtime
Even a very simple program is triggering this:
I'm not experiencing this with hdf5 version 1.14.0 My OS is : Ubuntu 22.04.2 LTS