-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Use -enable-ossa-modules for all of stdlib/public #39478
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 test |
@swift-ci benchmark |
Build failed |
1b2e607
to
67c509a
Compare
@swift-ci test |
@swift-ci benchmark |
Performance (x86_64): -O
Code size: -OPerformance (x86_64): -Osize
Code size: -OsizePerformance (x86_64): -Onone
Code size: -swiftlibs
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
|
67c509a
to
85c79de
Compare
@swift-ci test |
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.
I like the idea. If this sticks, can we get rid of all the special case modes for transparent functions and stdlib builds?
Do we still need this? Will the flag be passed twice to the stldib build now? |
With this, even non-transparent functions will have their ownership eliminated later in the pipeline
85c79de
to
974710e
Compare
@atrick Thanks. I got rid of it in the latest update.
Good point. I need to test this, but I think we still need these modes for the deserialization hooks we install in OME. |
@swift-ci test |
This will pass -enable-ossa-modules while compiling all of
stdlib/public
not juststdlib/public/core
.With this, even non-transparent functions will have their ownership eliminated later in the pipeline.