Skip to content

[SILOptimizer] Properly disconnect the signature optimized function from a parent class. #17539

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 1 commit into from
Jun 27, 2018

Conversation

huonw
Copy link
Contributor

@huonw huonw commented Jun 27, 2018

The new function with an optimized signature shouldn't have a non-trivial
classSubclassScope, even if the original function did, since the original
function (that becomes the thunk) is the symbol that serves that role.

Also part of rdar://problem/40738913

A missed case in #16959

@huonw
Copy link
Contributor Author

huonw commented Jun 27, 2018

@swift-ci please smoke test

…rom a parent class.

The new function with an optimized signature _shouldn't_ have a non-trivial
classSubclassScope, even if the original function did, since the original
function (that becomes the thunk) is the symbol that serves that role.

Also part of rdar://problem/40738913
@huonw huonw force-pushed the tbd-thunk-specialization branch from 1e5ffe2 to 85424c0 Compare June 27, 2018 02:09
@huonw
Copy link
Contributor Author

huonw commented Jun 27, 2018

@swift-ci please smoke test

@huonw huonw merged commit a7b4e0f into swiftlang:master Jun 27, 2018
@huonw huonw deleted the tbd-thunk-specialization branch June 27, 2018 03:51
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.

1 participant