Skip to content

[CopyPropagation] Removed poison mode. #61344

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

Conversation

nate-chandler
Copy link
Contributor

The -Onone strategy will be to shorten lifetimes as little as possible while eliminating as many copies as are eliminated at -O.

The Onone strategy will be to shorten lifetimes as little as possible
while eliminating as many copies as are eliminated at -O.
@nate-chandler
Copy link
Contributor Author

@swift-ci please test

Copy link
Contributor

@atrick atrick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you should go ahead and remove this mode since it will make refactoring the code easier.

I'm almost certain we have a new way of emitting DWARF to indicate when a variable's lifetime ends. So we should no longer need to write a poison marker into the shadow variable's stack slot. /cc @adrian-prantl

@nate-chandler
Copy link
Contributor Author

@swift-ci please test windows platform

@nate-chandler nate-chandler merged commit 4dec193 into swiftlang:main Sep 29, 2022
@nate-chandler nate-chandler deleted the copy-propagation/remove-poison branch September 29, 2022 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants