Some small optimizer tweaks #42191
Merged
Some small optimizer tweaks #42191
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
…estroy/release instruction * C++: add a function `getDestructors(SILType type, bool isExactType)’: if the type is a final class or `isExactType` is true, then return the one and only destructor of that class. * swift: add `getDestructor(ofExactType type: Type)` and `getIncompleteCallees` * swift: remove `getDestructor` from the PassContext. The API of the `calleeAnalysis` can be used instead.
We already do this for `strong_release` and `release_value`, but `destroy_value` was missing
|
@swift-ci test |
|
@swift-ci benchmark |
|
@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.
destroy_valueThese small improvements are a preparation for the new escape analysis (#39438) - and will be mostly tested by that changes.