Open edwardhartnett opened 3 months ago
Presumably this is the same issue as this: https://github.com/Unidata/netcdf-c/issues/2700
So I suppose the stanza introduced in https://github.com/Unidata/netcdf-c/pull/2935/files is either not being entered, or the -fhonor-infinities
flag is not doing what is expected. @edwardhartnett can you pass -fhonor-inifinities
to the compiler and see if that addresses the issue on your end? If so, I'll check the conditional, if not, I'll look more into compiler flags.
I will try when I can log in again - some problem with the system this morning.
The Intel oneapi is freely available and can be tested in the CI. We do that with the NCEPLIBS libraries here at NOAA. My colleague @AlexanderRichert-NOAA has made a GitHub action which installs the Intel compilers on a test instance. Take a look here, I think you could just use it directly, or take your own copy: https://github.com/NOAA-EMC/ci-install-intel-toolkit
I will take a look at integrating that, thanks!
I'm working on the next Fortran release, so that might be a good time to integrate modern alternatives to gfortran.
But it should be noted that the problem described in this issue was in the C library...
It should be noted indeed, and should have been obvious; as you can tell, I've been focused on the Fortran release XD. Yes, I will take a look at this in the C library.
I'm also going to do some netcdf-fortran tests after the netcdf-c testing I'm doing.
I was just reflecting on the value of unit tests to the netCDF project. Here we have code written in some cases 15 or 20 years ago, still working very well on new compilers, new systems, all with a small staff - and netCDF continues to add new features at an impressive rate. After all this time, the original v2 test code still runs perfectly. It's a record any software project would envy...
This is with the latest code from main (updated today).
The intel oneapi compiler seems to have broken some infinities(?):