-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[CanonicalizeOSSALifetime] Run on lexical lifetimes. #63606
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
nate-chandler
merged 6 commits into
swiftlang:main
from
nate-chandler:canonicalize_ossa_lifetime/lexical_values
Mar 27, 2023
Merged
[CanonicalizeOSSALifetime] Run on lexical lifetimes. #63606
nate-chandler
merged 6 commits into
swiftlang:main
from
nate-chandler:canonicalize_ossa_lifetime/lexical_values
Mar 27, 2023
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
3ca1472
to
1034d65
Compare
atrick
reviewed
Feb 23, 2023
46970df
to
a6bd234
Compare
027dd25
to
989faa0
Compare
@swift-ci please test |
@swift-ci please benchmark |
@swift-ci please test macos platform |
1 similar comment
@swift-ci please test macos platform |
|
989faa0
to
5182539
Compare
@swift-ci please test |
atrick
approved these changes
Mar 24, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome!
A couple of suggestions...
cb84bd4
to
bc382f4
Compare
@swift-ci please test |
Allow clients to specify any number (an array) of blocks beyond which dataflow won't propagate rather than 1 or 0 (a pointer).
Adapt a preexisting test to be a unit test that runs the utility.
@swift-ci please test |
If multiple terminators which branch to the same merge block are added to the boundary, depending on whether a destroy_value can be found within the block either (a) every terminator must be added to the boundary or (b) the destroy_value must be added to the boundary exactly once.
bc382f4
to
b9960b7
Compare
@swift-ci please test |
Previously, the utility bailed out on lexical lifetimes because it didn't respect deinit barriers. Here, deinit barriers are found and added to liveness if the value is lexical. This enables copies to be propagated without hoisting destroys over deinit barriers. rdar://104630103
b9960b7
to
ec3f005
Compare
@swift-ci please test |
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.
Previously, the utility bailed out on lexical lifetimes because it didn't respect deinit barriers. Here, deinit barriers are found and added to liveness if the value is lexical. This enables copies to be propagated without hoisting destroys over deinit barriers.
rdar://104630103