Don't emit atomics for thread-safe assignment patterns #401
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.
This attempts to fix #316.
It prevents a
#pragma omp atomic
from being emitted for the assignment toy_vals[i]
in this case:Because each thread gets its own value of
i
, no other thread will assign to that location, and recent compilers treat an atomic pragma as invalid there. See #316 for details.Are there any other cases this doesn't cover? All tests pass for me when configuring with
-DOPENMP=ON -DPYTHON=ON
.