-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Caching] Use subInvocation to verify interface #71497
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
[Caching] Use subInvocation to verify interface #71497
Conversation
@swift-ci please smoke test |
Please test with following pull request: @swift-ci please smoke test |
a8c4100
to
ef24ffc
Compare
Please test with following pull request: @swift-ci please smoke test |
ef24ffc
to
397c82f
Compare
Please test with following pull request: @swift-ci please smoke test |
397c82f
to
cead485
Compare
Please test with following pull request: @swift-ci please smoke test |
Please test with following pull request: @swift-ci please smoke test macOS platform |
1 similar comment
Please test with following pull request: @swift-ci please smoke test macOS platform |
cead485
to
dd4104c
Compare
Please test with following pull request: @swift-ci please smoke test |
Clean up how CASOptions are kept and passed inside swift to make the code more readable. Also avoid a copy of CAS configuration in ClangImporter.
The interface verification needs to read some command-line from the interface file so it needs to be built inside sub-invocation. rdar://122423965
dd4104c
to
ebc90ff
Compare
Please test with following pull request: @swift-ci please smoke test |
ping |
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.
Looks great.
The interface verification needs to read some command-line from the interface file so it needs to be built inside sub-invocation.
rdar://122423965