-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Handle store_borrow in SILMem2Reg and some other fixes #59541
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
Conversation
@swift-ci test |
9d156da
to
158b0bd
Compare
@swift-ci benchmark |
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.
Thanks for working on this. Let's see if there's a way to keep the original "borrow" semantics without copies. We need to store move-only values in store-borrow locations.
@nate-chandler can we also get your eyes on this and together come up with something that integrates well with the new support for lexical scopes?
…ad of computing in-place
158b0bd
to
0a7c7f3
Compare
@swift-ci test |
@swift-ci benchmark |
@swift-ci test source compatibility |
0a7c7f3
to
2e4f48f
Compare
@swift-ci test |
@atrick @nate-chandler Mem2Reg for store_borrows is straight forward now that I have fixed the store_borrow representation in SIL. |
5786abb
to
8c9c61a
Compare
@swift-ci test |
8c9c61a
to
ed7788f
Compare
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
@swift-ci test and merge |
@swift-ci test macOS Platform |
No description provided.