Merge pull request #2131 in HDFFV/hdf5 from ~LRKNOX/hdf5_lrk:hdf5_1_10 to hdf5_1_10
* commit 'b85582098c29aea59bbc7fe0287fe71cab998fe5':
Update version for HDF5_1_10
Merge pull request #2106 in HDFFV/hdf5 from ~BYRN/hdf5_adb:hdf5_1_10 to hdf5_1_10
* commit '5109ff1d84df2a4ee0493c196399e89e9fd0c10b':
Add missing include folder
Remove unneeded flag overwrites
Merging in latest from upstream (HDFFV/hdf5:refs/heads/hdf5_1_10)
* commit 'c58108ea4030e74a0b745cabbc8ccd366695de07':
Latest date first in RELEASE.txt
Update RELEASE.txt with performance improvements
Add fix of Jira 10934 to RELEASE.txt
Merge pull request #2120 in HDFFV/hdf5 from ~CHOGAN/hdf5:chogan/1.10/release_txt to hdf5_1_10
* commit '13e6094edabb8dcd1c52a20cab24f5d630616661':
Latest date first in RELEASE.txt
Update RELEASE.txt with performance improvements
Merge pull request #2111 in HDFFV/hdf5 from ~CHOGAN/hdf5:chogan/1.10/10934_release_txt to hdf5_1_10
* commit '8cd58add98994c8d30dce607a12a01e445e0bb4d':
Add fix of Jira 10934 to RELEASE.txt
Merging in latest from upstream (HDFFV/hdf5:refs/heads/hdf5_1_10)
* commit 'b00a52c403e4b7b64be974080ddfef3aee1bf801':
Fix the segmentation fault when h5dump "vds_virt_0.h5", which is a test file produced by test/vds.c in the develop branch. The fix: verify the decoded version for hyperslab selection is within the correct range.
Merging in latest from upstream (HDFFV/hdf5:refs/heads/hdf5_1_10)
* commit '3726715625d146ddffc4236b8de5cc601c87b737':
Add changes from PR #2049 to 1.10
Merging in latest from upstream (HDFFV/hdf5:refs/heads/hdf5_1_10)
* commit '91b2ae219cd631798f95f0a94e793f2a2366b618':
Set the dcpl for the context on dataset creation
Add DCPL to H5CX
Check for both default values
Use H5CX for LCPL property retrieval
Merging in latest from upstream (HDFFV/hdf5:refs/heads/hdf5_1_12)
* commit 'e399be1e9156840aa0664323dfc00a93ac43575c':
Complete the comment on thread_main(), explaining why the barrier is used.
The first implementation seemed to allow for the possibility that a thread could block at the barrier, wake and exit the barrier, re-acquire the barrier lock and increase `nentered` before the other blocked threads woke and checked `nentered % count == 0`. Then the other blocked threads would che...
Merge pull request #2575 in HDFFV/hdf5 from ~DYOUNG/werror:fix-thread_id-1_12 to hdf5_1_12
* commit 'f0485413e02ebf1117e5b1725f32534e7e26b622':
Complete the comment on thread_main(), explaining why the barrier is used.
The first implementation seemed to allow for the possibility that a thread could block at the barrier, wake and exit the barrier, re-acquire the barrier lock and increase `nentered` before the other blocked threads woke and checked `nentered % count == 0`. Then the other ...
The first implementation seemed to allow for the possibility that a thread
could block at the barrier, wake and exit the barrier, re-acquire the barrier
lock and increase `nentered` before the other blocked threads woke and checked
`nentered % count == 0`. Then the other blocked threads would check `nentered
% count == 0` and, finding it false, go back to sleep in the barrier. This new
implementation waits for a looser condition to obtain so that threads don't go
back to sleep in the barrier.
Remove tongue-in-cheek credit for Rusty Shackleford and Dale Alvin Gribble.
Delete the comment questioning whether pthread_mutex_lock is allowed
in a key destructor, since pthread_key_create(3) provides the answer:
There is no notion of a destructor-safe function. If an application
does not call pthread_exit() from a signal handler, or if it blocks any
signal whose handler may call pthread_exit() while calling async-unsafe
functions, all functions may be safely called from d...
Make sure that H5TS_thread_id() is available as either a function or a macro in
all configurations.
Previously it was neither declared nor defined in --disable-threadsafety
builds. The compiler's warning got lost in the noise---I first saw the issue
because my -Werror branch stopped compiling cold---and the tests still linked
and ran.
Merge pull request #2569 in HDFFV/hdf5 from ~BYRN/hdf5_adb:hdf5_1_12 to hdf5_1_12
* commit 'ce7ee643c6fe9eecdf02ee9efbd77b2e9aea6e2d':
disable pr action and enable fail fast
Correct filename
OESS-65 Fix packaging
Merging in latest from upstream (HDFFV/hdf5:refs/heads/hdf5_1_12)
* commit '943129f61000899e394b75405723a3f110a21205':
Add note to release notes.
Change thread IDs to uint64_t from unsigned long, per Quincey's suggestion.
Add thread_id.c to the MANIFEST and the CMakeLists.txt per Allen's request.
Replace pthread_self_ulong() with H5TS_thread_id(). The POSIX Threads implementation ought to be portable to any system that has POSIX Threads. On Windows, I use the same API call as befor...
Merge pull request #2567 in HDFFV/hdf5 from alloc_0sized_dset_fix_1_12 to hdf5_1_12
* commit '8dc9001a21cc3101059335a394e1f0bb7e3c3867':
Add note to release notes.
Change thread IDs to uint64_t from unsigned long, per Quincey's suggestion.
Add thread_id.c to the MANIFEST and the CMakeLists.txt per Allen's request.
Replace pthread_self_ulong() with H5TS_thread_id(). The POSIX Threads implementation ought to be portable to any system that has POSIX Threads. On Windows, I use the same...
