-
-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runtime failure in H5T__init_native_float_types() #4381
Comments
Hey, I believe this might be related to #3831? FYI: We experienced the same in conda-forge/code-aster-feedstock#57. I re-ran the compilation with hdf5=1.14.0 locally and the issue was gone. Hopefully this will be fixed in 1.14.4 (which I believe has a milestone freeze today). |
This should be fixed in 1.14.4, which releases today. The floating point exceptions are generated by our datatype introspection code, which runs at library startup. This used to be done in a separate program at compile time, but this made cross-compilation difficult, so now it's a runtime check. Please reopen if this isn't fixed in 1.14.4 and we'll investigate further |
Just tested with the hdf5_1_14_4 branch. The "floating invalid" error is gone. |
Describe the bug
I'm seeing a floating point exception while opening a NetCDF4 file with nf90_open(). A partial stack trace follows.
Expected behavior
otta work
Platform (please complete the following information)
1.14.3
SLES-15sp3
ftn and cc from the Cray build environment.
which cc
/opt/cray/pe/craype/2.7.17/bin/cc
cc --version
icc (ICC) 19.1.3.304 20200925
which ftn
/opt/cray/pe/craype/2.7.17/bin/ftn
ftn --version
ifort (IFORT) 19.1.3.304 20200925
Autotools
export FFLAGS="-g -O0 -traceback -fPIC -w"
export CFLAGS="-g -O0 -traceback -fPIC -w"
export CXXFLAGS="-fPIC -w"
export FCFLAGS="$FFLAGS"
--enable-fortran --enable-cxx --enable-build-mode=debug --with-zlib=/lfs/h1/hpc/support/daniel.kokron/Projects/hpc-stack/install/intel-19.1.3.304/zlib/1.2.11 --disable-shared --enable-static --enable-parallel --enable-unsupported
cray-mpich-8.1.20
Additional context
Add any other context about the problem here.
config.log
The text was updated successfully, but these errors were encountered: