[Cherry-Pick][BugFix][TIR] ThreadSync with shared.dyn awareness #15481
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.
Cherry-picked from #15478.
This PR fixes an issue of the ThreadSync pass.
Prior to this PR, the pass is not aware of
shared.dyn
scope whose users all share a same shared memory space. This feature is not necessarily already revealed in the IR at the time of applying ThreadSync. This means that when applying ThreadSync, in the IR, each buffer ofshared.dyn
scope still uses its own data Var, and ThreadSync is thus unable to detect the conflict properly and insert the sync instructions properly.This PR explicitly makes ThreadSync be aware of the
shared.dyn
scope, and redirect all the access vars ofshared.dyn
memory to a common var, so that ThreadSync analysis can find out the conflict and insert the sync instructions.