| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
* Remove user presets file
* Only use C compiler for sanitzers
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
This is not used in the library
|
|
|
|
|
|
|
| |
There are many architecture-specific linux files in the config
directory, all of which simply redirect to linux-gnulibc1.
This change renames linux-gnulibc1 to linux-gnu and deletes the more
specific files.
|
|
|
|
| |
The ibm-aix Autotools config file had some unmaintained and unnecessary
Autoconf cache overrides. These have been removed.
|
|
|
|
|
|
|
| |
The Autools Classic Intel compiler configuration attempts to load a file
named `general-19` from the intel-warnings/classic directory, which does
not exist.
This removes the attempted load of the file.
|
| |
|
|
|
| |
Add a new testing function to verify C_BOOL values.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* Update INSTALL_CMake.txt as necessary
* Update remaining docs that use HDF5_USE_GNU_DIRS
* Update options in HDFMacros in HDF5Examples
|
|
|
|
|
| |
*autom4te* to release tar & zip files. (#4009)
Filter messages with 'ulimit -s' out of test output for runTest.cmake.
|
|
|
|
|
| |
* revert to using c-stub for _F08 MPI APIs
* use mpi compiler wrappers for cmake and nvhpc
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Reorg and update options for doc and cmake config
* Correct subfiling depends
* Add linux S3 binaries to GH published files
* Correct path
* Try reducing parallel jobs in tests
* Change examples jobs for test from 8 to 4
|
|
|
|
| |
* Reorg and update options for doc and cmake config
* Correct subfiling depends
|
| |
|
|
|
|
|
|
|
|
|
| |
* Add 'warning density' computation to the warnhist script, along with several
cleanups to it. Add "--enable-show-all-warnings" configure (and CMake)
option to disable compiler diagnostic suppression (and therefore show all the
otherwise suppressed compiler diagnostics), disabled by default. Clean up
a buncn of misc. warnings.
Signed-off-by: Quincey Koziol <qkoziol@amazon.com>
|
|
|
|
|
|
|
|
|
| |
* Fix missing build-mode value
* Use 110 version file only for the 1.10 library
* Fix H5_LIBVER_DIR variable
* Disable 1.6 API tests for now.
|
|
|
|
|
|
|
|
| |
* Choose a size for rdata dimension
* Fix platform naming conflicts
* Fix doxygen references to point within library repo
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Fixes:
checking for config freebsd12.1... no
checking for config freebsd... found
compiler '/home/svcpetsc/petsc-hash-pkgs/39f577/bin/mpicc' is GNU gcc-9.2.0
compiler '/home/svcpetsc/petsc-hash-pkgs/39f577/bin/mpif90' is GNU gfortran-9.2.0
stdout: .: cannot open ./config/classic-fflags: No such file or directory
|
|
|
|
|
|
|
| |
* Update examples with 1.6 api and static libs
* Only check for STATIC only builds
* Do not calculate version as library has already.
|
|
|
|
|
|
|
|
|
| |
* Merge examples repo into library
* Change grepTest to be more fault-tolerant
* Update examples macro file
* Exclude all Fortran examples from doxygen
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
HDF5 performs a couple of checks at build time to see if long double
values can be converted correctly (IBM's Power architecture uses a
special format for long doubles). These checks were performed using
TRY_RUN, which is a problem when cross-compiling.
These checks now use default values appropriate for most non-Power
systems when cross-compiling. The cache values can be pre-set if
necessary, which will preempt both the TRY_RUN and the default.
Affected values:
H5_LDOUBLE_TO_LONG_SPECIAL (default no)
H5_LONG_TO_LDOUBLE_SPECIAL (default no)
H5_LDOUBLE_TO_LLONG_ACCURATE (default yes)
H5_LLONG_TO_LDOUBLE_CORRECT (default yes)
H5_DISABLE_SOME_LDOUBLE_CONV (default no)
Fixes GitHub #3585
|
| |
|
| |
|
|
|
|
|
|
|
| |
The H5T floating-point datatype initialization code can raise exceptions when handling signaling NaNs. This change disables FE_INVALID exceptions during initialization.
Also removes the -ieee=full change for NAG Fortran as that shouldn't be necessary anymore.
Fixes #3831
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Set NVHPC maximum optimization level to -O1 for now
Compiling HDF5 with NVHPC 23.5 - 23.9 results in test failures in
4 different test files that need to be resolved. Since those tests
pass with an optimization level of -O1 (and -O0) and it is currently
unclear whether the test failures are due to issues in HDF5 or issues
in the 'nvc' compiler, set the maximum optimization level for NVHPC
to -O1 until the test failures are resolved.
* Disable nvhpc Java testing in CMake and amend known issues
* Re-enable testing of Autotools nvhpc
|
| |
|
|
|
| |
* Disable testing as tests are failing the same as in CMake
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Update Autotools to correctly configure oneAPI
Splits the Intel config files under the Autotools into 'classic'
Intel and oneAPI versions, fixing 'unsupported option' messages.
Also turns off `-check uninit` (new in 2023) in Fortran, which kills
the H5_buildiface program due to false positives.
* Enable Fortran in oneAPI CI workflow
* Turn on Fortran in CMake, update LD_LIBRARY_PATH
* Go back to disabling Fortran w/ Intel
For some reason there's a linking problem w/ Fortran
error while loading shared libraries: libifport.so.5: cannot open shared object file: No such file or directory
|
| |
|
|
|
|
|
|
| |
* Split intel compiler flags into sub-folders
* Update Intel options for warnings
* Mostly CMake, Autotools needs additional work
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Correct use of set() command with options
* Force filter off if not found
Co-authored-by: Allen Byrne <50328838+byrnHDF@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Adds a config/clang-fflags options file to support Flang
* Corrects missing "-Wl," from linker options in the libtool wrappers
when using Flang, the MPI Fortran compiler wrappers, and building
the shared library. This would often result in unrecognized options
like -soname.
* Enable -nomp w/ Flang to avoid linking to the OpenMPI library.
CMake can build the parallel, shared library w/ Fortran using AOCC
and Flang, so no changes were needed for that build system.
Fixes GitHub issues #3439, #1588, #366, #280
|
|
|
|
|
|
|
| |
* added cmake ieee flag for nagfor
* generalized determining the nag compiler
* fixing some misc. NAG warnings
|
|
|
| |
* synchronize TGZ naming convention/usage
|