| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
These will never pass `make check` and would require a custom test
suite for more comprehensive testing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add cygwin CI
* add cygwin packages
* Correct option names
* Cleanup yaml file and synch look and feel
* Synch CI look and feel and correct path issues
* Upgrade oneapi version
* pwsh needs env: for vars
* No continuation char for pwsh
* restore correct pwsh step
* Run subset of tests for cygwin workflow
* Remove space chars in regex
* restore full tests
|
| |
|
|
|
| |
Was missng the 2008 pread/write info
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Externally visible:
* The HDF_ENABLE_LARGE_FILE option (advanced) has been removed
* We no longer run a test program to determine if LFS works, which
will help with cross-compiling
* On Linux we now unilaterally set -D_LARGEFILE_SOURCE and
-D_FILE_OFFSET_BITS=64, regardless of 32/64 bit system. CMake
doesn't offer a nice equivalent to AC_SYS_LARGEFILE and since
those options do nothing on 64-bit systems, this seems safe and
covers all our bases. We don't set -D_LARGEFILE64_SOURCE since
we don't use any of the POSIX 64-bit specific API calls like
ftello64, as noted above.
* We didn't test for LFS support on non-Linux platforms. We've added
comments for how LFS should probably be supported on AIX and Solaris,
which seem to be alive, though uncommon. PRs would be appreciated if
anyone wishes to test this.
Internal:
* Drops off64_t size checks since this is unused (as in Autotools)
* Remove HDF_EXTRA_FLAGS, which is now unused
* Remove hack around deprecated LINUX_LFS
Fixes #2395
|
|
|
|
|
| |
ratios (#4083)
Rework TEST_FILTER tests to handle slightly different compression ratios
|
| |
|
|
|
| |
It was introduced in MSVC 15 (Visual Studio 2017).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The H5B (version 1 B-tree) package would add some computationally
expensive integrity checks when H5B_DEBUG was defined. Due to their
negative effects on performance, this option was rarely turned on,
making the H5B__assert() check function stale, if not dead, code.
This change:
* Builds H5B__assert() when NDEBUG is not defined (the function
relies on assert()) so it gets compiled more often.
* Removes some printf debugging statements in the B-tree code
* Removes all H5B "extra debug" checks that are leftover from
past debugging sessions. Maintainers can add H5B__assert()
selectively to perform integrity checks when debugging.
* Removes the HDF5_ENABLE_DEBUG_H5B CMake option
H5B_DEBUG now has no effect
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Added Fortran H5E APIs:
h5eregister_class_f, h5eunregister_class_f, h5ecreate_msg_f, h5eclose_msg_f
h5eget_msg_f, h5epush_f, h5eget_num_f, h5ewalk_f, h5eget_class_name_f,
h5eappend_stack_f, h5eget_current_stack_f, h5eset_current_stack_f, h5ecreate_stack_f,
h5eclose_stack_f, h5epop_f, h5eprint_f (C h5eprint v2 signature)
Addresses Issue #3987
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Rename incorrectly named option
* Restore the correct uses of USING_MEMCHECKER
* Update release note
|
|
|
|
|
| |
* 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
|
| |
|