Don't use atomic_thread_fence under TSAN #544
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TSAN is one of the best tools for checking correctness of concurrent programs out there, but sadly, it does not support atomic_thread_fence and unlikely ever will. But for good codegen on ARM we NEED atomic_thread_fence in shared_ptr. Hence, we need to selectively use it only when TSAN is disabled and fallback to an unconditional acq_rel operation where the ARM acquire fence will be performed even when we are not releaseing the last reference. This is pretty much equivalent semantically, but avoids false-positive TSAN reports.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
TSAN is one of the best tools for checking correctness of concurrent programs out there, but sadly, it does not support atomic_thread_fence and unlikely ever will.
But for good codegen on ARM we NEED atomic_thread_fence in shared_ptr. Hence, we need to selectively use it only when TSAN is disabled and fallback to an unconditional acq_rel operation where the ARM acquire fence will be performed even when we are not releaseing the last reference. This is pretty much equivalent semantically, but avoids false-positive TSAN reports.
Tackles #543.