diff options
author | Larry Knox <lrknox@hdfgroup.org> | 2020-03-24 13:22:25 (GMT) |
---|---|---|
committer | Larry Knox <lrknox@hdfgroup.org> | 2020-03-24 13:22:25 (GMT) |
commit | 8890fa3eb51fc47e79a9ac3dd0247ef2cc472f72 (patch) | |
tree | 602058ad6717f67d5a70ec690043175292c87350 /bin/runbkgprog | |
parent | d9f93659a28ecae44e298c8ef80fe63f70810d0d (diff) | |
parent | d3ef866a2963ce93d0b95184534a70849b6fa11d (diff) | |
download | hdf5-8890fa3eb51fc47e79a9ac3dd0247ef2cc472f72.zip hdf5-8890fa3eb51fc47e79a9ac3dd0247ef2cc472f72.tar.gz hdf5-8890fa3eb51fc47e79a9ac3dd0247ef2cc472f72.tar.bz2 |
Merging in latest from upstream (HDFFV/hdf5:refs/heads/develop)
* commit 'd3ef866a2963ce93d0b95184534a70849b6fa11d':
Revise API for H5get_alloc_stats() to take a struct instead of separate values.
Move the GNU warnings configuration under config/gnu-warnings/ and trim the filename prefixes. Update config/gnu-flags to suit.
Fixed the RELEASE.txt note for HDFFV-11057
Fix shutdown errors when using the HDF5_VOL_CONNECTOR environment variable to set a dynamically loaded plugin as the default VOL connector. Fixes HDFFV-11057
Fix threadsafe for new test
Fix issues when deserializing point/all/none selection with version beyond the library's supported version: (1) Verify the decoded version before proceeding further with deserialization (2) Close the dataspace if errors occurred after opening the dataspace
Very minor comment change in H5VLconnector.h.
Add routines to query the library's free list sizes and allocation stats.
By default, demote warnings promoted to errors back to warnings.
Incorporate the H5_ECFLAGS into the library CFLAGS. Now a bunch of errors will occur. Next commit will demote the warnings promoted to errors back to warnings again.
Break out warnings into more files that autoconf and CMake can share. This change temporarily disables the warnings that were promoted to errors, but I will add those warnings back as warnings, not errors, in the next commit.
Avoid a crash, don't check if we're flushing when the file is closing: there's no need to check if the metadata cache is flushing if we already know the file is closing, because the condition we rely on is "closing OR flushing." Further, the cache may have already gone away, so sometimes calling into the cache to see if it's flushing will crash the program.
Diffstat (limited to 'bin/runbkgprog')
0 files changed, 0 insertions, 0 deletions