[XLA:MSA] Fixes an issue that leads to sync mem op replacements not respecting the auxiliary control dependencies while converting sync mem ops to async #23276
+63
−0
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.
[XLA:MSA] Fixes an issue that leads to sync mem op replacements not respecting the auxiliary control dependencies while converting sync mem ops to async
MSA assumes all control dependencies (predesseccors/successors) are met in earlier passes by the scheduler. Therefore, it traditionally only respects the data flow dependencies (i.e., instruction.uses()). This became problematic when we replaced sync copies with async ones: the async copies where not aware of indirect control dependencies when we were determining their latest allowed copy-done time.