[OpenMP] Add sanity check for concurrent taskgraph reset#195076
Open
Conversation
Created using spr 1.3.5
|
✅ With the latest revision this PR passed the C/C++ code formatter. |
This was referenced May 1, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 patch adds a sanity check for concurrent taskgraph re-recording:
the case where two threads might simultaneously hit a taskgraph region
with the same graph_id and a non-zero graph_reset clause.
This will only trigger when debugging/assertions are enabled: it might
be more helpful to do this check unconditionally, but I'm not sure what
sort of error path in libomp should be used in that case.