-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[4.2] Cherry-pick dropping @inlinable and other cleanup #16593
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 test |
@swift-ci please benchmark |
@swift-ci please test compiler performance |
@eeckstein, @lorentey this is a 4.2 cherry-pick of the other PRs |
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.
lgtm
Build failed |
Build comment file:Build failed before running benchmark. |
!!! Couldn't read commit file !!! |
@swift-ci please test linux platform |
Build failed |
@swift-ci please test linux platform |
Build failed |
Aggressively remove all `@inlinable` from any function that's `@inline(never)` to see the impact. `@inlinable @inline(never)` is a potential code smell. While it might expose some optimization and specialization opportunities to the optimizer, it's most commonly a sign that more thought is needed.
Dropping many of Array's @inlinable annotations caused some performance regressions. Restore them temporarily while we figure out how to better annotate these decls.
Done to address benchmark regressions.
#16850 Included most of these. Still have the Array ones though... |
…ration We have no generic environment in this case, and just need to print the canonical generic parameter types. Fixes <https://bugs.swift.org/browse/SR-7673>.
@swift-ci test |
Build failed |
This is a cherry-pick of #16578 and #16477