-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[DependencyScanning] Use clang scanner callback to speed up bridging #81454
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
base: main
Are you sure you want to change the base?
[DependencyScanning] Use clang scanner callback to speed up bridging #81454
Conversation
Please test with following PR: @swift-ci please smoke test |
cc78976
to
482f194
Compare
@swift-ci please smoke test |
Please test with following PR: @swift-ci please smoke test |
482f194
to
0aba426
Compare
Please test with following PR: @swift-ci please smoke test |
0aba426
to
8072d19
Compare
Please test with following PR: @swift-ci please smoke test |
Please test with following PR: @swift-ci please smoke test macOS platform |
1 similar comment
Please test with following PR: @swift-ci please smoke test macOS platform |
Use the underlying compiler invocation inside module scanning result to speed up the clang module dependency bridging. This avoids converting cc1 arguments to compiler invocation and back, just to modify the cc1 arguments needed for building PCM using swift-frontend. rdar://151705822
8072d19
to
391446d
Compare
Please test with following PR: @swift-ci please smoke test macOS platform |
Please test with following PR: @swift-ci please smoke test |
Use the new callback function in clang scanner to transform the build command to speed up the build. Currently, there is quite some overhead to round-trip all the clang module build commands in order to transform them for swift builds using a single thread. The API allows cheap command-line transform through clang::CompilerInvocation interface.
rdar://151705822