summaryrefslogtreecommitdiffstats
path: root/testpar
diff options
context:
space:
mode:
authorLarry Knox <lrknox@hdfgroup.org>2020-02-28 12:22:13 (GMT)
committerLarry Knox <lrknox@hdfgroup.org>2020-02-28 12:22:13 (GMT)
commitd7eec7d6ec721ce34ccd32a75261e7711bd3ee1b (patch)
tree2f0aa7b3a06556f99a9d23fce747739d0113b547 /testpar
parentcfc52fc273a098ffa0cd10f41a9b4191e1f38f16 (diff)
parent803d805c74466a9d736455930b17de2d9f5cb02d (diff)
downloadhdf5-d7eec7d6ec721ce34ccd32a75261e7711bd3ee1b.zip
hdf5-d7eec7d6ec721ce34ccd32a75261e7711bd3ee1b.tar.gz
hdf5-d7eec7d6ec721ce34ccd32a75261e7711bd3ee1b.tar.bz2
Merge pull request #2411 in HDFFV/hdf5 from ~DYOUNG/werror:darwin-barriers to develop
* commit '803d805c74466a9d736455930b17de2d9f5cb02d': 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 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. Test the right condition for the EBUSY return in pthread_barrier_destroy(). s/exit_failure/EXIT_FAILURE/g Implement pthread_barrier(3) for Darwin using a counter, condition variable, and mutex. Untested.
Diffstat (limited to 'testpar')
0 files changed, 0 insertions, 0 deletions