-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Fix InteriorUseWalker: consider partial_apply [on_stack] an escape #85934
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
Open
atrick
wants to merge
1
commit into
swiftlang:main
Choose a base branch
from
atrick:fix-closure-liveness
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+37
−2
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
Fixes a bug in MandatoryDestroyHoisting where a captured value is destroyed before a copy of the closure. On-stack closures can be copied, and all copied uses must be within the borrow scope of the captured operand. This is just like any other non-Escapable value, so treat it as such by checking `Value.mayEscape` rather than `Type.Escapable`. Originally, I wanted to make it illegal to copy of partial_apply [on_stack], but it looks like we still allow it. I would rather not complicate any logic yet with special handling for this case. To fix any performance concerns, we might be able to simplify the representation instead by banning copy_value on on-stack closures. Fixes rdar://165850554 swift-frontend crash: While running "CopyPropagation" - Invalid SIL provided to OSSACompleteLifetime?!)
Contributor
Author
|
@swift-ci test |
Contributor
Author
|
@swift-ci benchmark |
Contributor
Author
|
@swift-ci test linux |
meg-gupta
approved these changes
Dec 9, 2025
Contributor
meg-gupta
left a comment
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.
LGTM
Contributor
|
@swift-ci test macOS platform |
eeckstein
approved these changes
Dec 10, 2025
Contributor
Author
|
This has no impact on the benchmark scores |
Contributor
Author
|
TIMEOUT: lldb-api :: functionalities/tsan/swift-access-race/TestTsanSwiftAccessRace.py |
Contributor
Author
|
@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.
Fixes a bug in MandatoryDestroyHoisting where a captured value is destroyed
before a copy of the closure.
On-stack closures can be copied, and all copied uses must be within the borrow
scope of the captured operand. This is just like any other non-Escapable value,
so treat it as such by checking
Value.mayEscaperather thanType.Escapable.Originally, I wanted to make it illegal to copy of partial_apply [on_stack], but
it looks like we still allow it.
I would rather not complicate any logic yet with special handling for this
case. To fix any performance concerns, we might be able to simplify the
representation instead by banning copy_value on on-stack closures.
Fixes rdar://165850554 swift-frontend crash: While running "CopyPropagation" -
Invalid SIL provided to OSSACompleteLifetime?!)