-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[stdlib] Audit inlinability in BridgeObjectiveC [WIP] #20470
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 Please benchmark |
@swift-ci Please smoke test |
7cee8f6
to
70700cf
Compare
@swift-ci Please test |
@swift-ci Please benchmark |
@@ -166,16 +166,17 @@ public func _bridgeAnythingToObjectiveC<T>(_ x: T) -> AnyObject { | |||
} | |||
|
|||
@_silgen_name("") |
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.
What is this doing?
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.
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.
The description there sounds a lot like @usableFromInline
, but quite possible @_silgen_name("")
has some other effects I'm not aware of.
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.
Oof, so we're using the usableFromInline-ness but also the ability to have such a function without a body. I guess that can't change for now.
<rdar://problem/45949961>
70700cf
to
ef1050f
Compare
@swift-ci Please benchmark |
Build comment file:Performance: -O
Code size: -O
Performance: -Osize
Code size: -Osize
How to read the dataThe tables contain differences in performance which are larger than 8% and differences in code size which are larger than 1%.If you see any unexpected regressions, you should consider fixing the Noise: Sometimes the performance results (not code size!) contain false Hardware Overview
|
@swift-ci Please test |
@swift-ci Please test |
rdar://problem/45949961