Skip to content

SILGen: Handle reabstraction in attempted +0 argument peephole. #18501

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
merged 2 commits into from
Aug 4, 2018

Conversation

jckarter
Copy link
Contributor

@jckarter jckarter commented Aug 3, 2018

When we saw a 'let' property of a class, then emitRValueForStorageLoad would give back the loaded borrowed property as-is without checking for reabstraction first. Fall back to copying and reabstracting in this case. Fixes rdar://problem/41056468.

Not building 32-bit slices saves some time during development when doing iOS builds for things that don't particularly care about bitness.
When we saw a 'let' property of a class, then `emitRValueForStorageLoad` would give back the loaded borrowed property as-is without checking for reabstraction first. Fall back to copying and reabstracting in this case. Fixes rdar://problem/41056468.
@jckarter jckarter requested a review from gottesmm August 3, 2018 21:04
@jckarter
Copy link
Contributor Author

jckarter commented Aug 3, 2018

@swift-ci Please test

@jckarter
Copy link
Contributor Author

jckarter commented Aug 3, 2018

@swift-ci Please test source compatibility

Copy link
Contributor

@gottesmm gottesmm left a comment

Choose a reason for hiding this comment

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

LGTM

@jckarter jckarter merged commit d924be3 into swiftlang:master Aug 4, 2018
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