AliasAnalysis: consider memory effects of a consume/destroy of a class on it's let-fields #78754
Conversation
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
…s on it's let-fields Although a let-field can never be mutated, a release or consume of the class must be considered as writing to such a field. This change removes the special handling of let-fields in two places, where they don't belong. Class fields are handled by ImmutableScope anyway. Handling of global let-variable is temporarily removed by this commit. Fixes a miscompile. rdar://142996449
Global let-variables are immutable, except in functions which initialize them. This brings back handling of global let-variables in alias analysis, which was removed in the previous commit.
|
@swift-ci test |
|
@swift-ci apple silicon benchmark |
|
@swift-ci test macos |
|
@swift-ci smoke test macos |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Although a let-field can never be mutated, a release or consume of the class must be considered as writing to such a field.
This change removes the special handling of let-fields in two places, where they don't belong.
Class fields were handled by ImmutableScope anyway. I added handling of global let-variable in ImmutableScope, too.
Fixes a miscompile.
rdar://142996449