Skip to content

[+0-normal-args] When forcing an argument into memory when performing… #14638

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

gottesmm
Copy link
Contributor

… a translating transform thunk, make sure it is at +1.

Fixes an issue where it was possible for a +0 pointer from an argument to get to
this thunk transform code. This is significantly more likely to happen when all
arguments are at +0.

This is tested by a SILGen test that I updated out of tree. It shouldn't effect
normal +1 code.

rdar://34222540

… a translating transform thunk, make sure it is at +1.

Fixes an issue where it was possible for a +0 pointer from an argument to get to
this thunk transform code. This is significantly more likely to happen when all
arguments are at +0.

This is tested by a SILGen test that I updated out of tree. It shouldn't effect
normal +1 code.

rdar://34222540
@gottesmm
Copy link
Contributor Author

@swift-ci smoke test and merge

@swift-ci swift-ci merged commit de617e7 into swiftlang:master Feb 14, 2018
@gottesmm gottesmm deleted the pr-e1619ccbacf71f7743e6bdab88cdb0d6ad7708b1 branch February 14, 2018 19:28
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