[EscapeAnalysis] Handle atomic instructions in escape analysis #71997
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.
Given the following simple use of the new
Atomic
type:we generate the following SIL:
TempLValueOpt is unable to eliminate the temporary because of the atomic builtin instruction acting as a barrier for escape analysis to determine if the zero initializer escapes the lexical alloc stack instruction. Handle them by walking down their result uses.
This results in the following new SIL:
Now, we should be able to optimize away the zero initializer entirely, but that's work for a different optimization pass.