This repository has been archived by the owner on Mar 21, 2024. It is now read-only.
Barrier parity waiting and algorithm tweaks #69
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds the ability to wait on a barrier when having only retained phase parity information (from domain knowledge, it isn't recoverable from the barrier object or its tokens), like so:
Also changed the algorithm so that some
b.arrive();
can be equivalent to just afetch_add
on its constituent atomic. These are available with the__expect_extra_arrive
and__extra_arrive
members.The parity waiting part isn't ABI breaking, but the algorithm tweak is ABI breaking because it halves the value of
::max()
, to half of int max (which is somewhat theoretical an issue given how large this number is). I didn't add ABI handling code.