-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[SILOptimizer] Stop optimization after serialization if only emitting a module #20986
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
d436b55
to
4d3dff6
Compare
This should not change the benchmarks at all. @swift-ci please benchmark |
Build comment file:No performance and code size changes |
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.
Needs a test case! (You can get the compiler to print what passes it's running.)
4d3dff6
to
b137928
Compare
@swift-ci please smoke test |
@swift-ci please benchmark |
Build comment file:No performance and code size changes |
LLDB failure is unrelated. @swift-ci please test macOS platform |
Build failed |
@swift-ci please smoke test |
@swift-ci please smoke test |
1 similar comment
@swift-ci please smoke test |
This is an experiment to stop the compilation pipeline after we've serialized a SIL module. There are a bunch of optimizations that happen after serialization whose results are tossed completely.
There are some modest wins here for compiling the stdlib with
-emit-module -O
(measured on an iMac Pro)