-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Fix recent class accessor performance regression #7485
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
slavapestov
merged 2 commits into
swiftlang:master
from
slavapestov:class-accessor-performance-regression
Feb 15, 2017
Merged
Fix recent class accessor performance regression #7485
slavapestov
merged 2 commits into
swiftlang:master
from
slavapestov:class-accessor-performance-regression
Feb 15, 2017
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… be transparent In 74d979f, the policy was changed so that only value type accessors are ever marked transparent, and not class accessors. This was intended to fix a bug where inlining an accessor of an Objective-C-derived class across module boundaries caused a linker failure because the accessor referenced a field offset variable, which has hidden visibility. However, this also caused a performance regression for Swift native classes. Bring back the old behavior for Swift native classes in non-resilient modules. Fixes <rdar://problem/29884727>.
Contributor
Author
|
@swift-ci Please test |
Contributor
Author
|
@swift-ci Please benchmark |
Contributor
Author
|
@eeckstein Does this look OK for 3.1? The first patch has no functional effect and just speeds up repeated Objective-C ancestry queries -- we don't have to pull it into 3.1. |
Contributor
Build comment file:Optimized (O) Regression (2)
Improvement (2)
No Changes (168)
Regression (3)
Improvement (5)
No Changes (164)
|
Contributor
|
LGTM! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should fix the performance regression introduced by #6400 by making stored property accessors of Swift-native classes @_transparent again.
When resilience is enabled these accessors are not transparent, so we might need to think of a way to recover the performance some other way eventually.
Fixes rdar://problem/29884727.