-
Notifications
You must be signed in to change notification settings - Fork 10.5k
fix calls to llvm prefix mapping functions to use space-separated opt… #81792
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
fix calls to llvm prefix mapping functions to use space-separated opt… #81792
Conversation
Please test with following pull request: @swift-ci Please test |
ef91ae4
to
e8cf513
Compare
Please test with following pull request: @swift-ci Please test |
Please test with following pull request: @swift-ci Please smoke test macOS platform |
Please test with following pull request: @swift-ci Please smoke test Windows |
@swift-ci please test macOS platform |
Please test with the following pull request: @swift-ci please test macOS platform |
4e3053e
to
d0c78c0
Compare
Please test with the following pull request: @swift-ci please test |
d0c78c0
to
7090b7e
Compare
Please test with the following pull request: @swift-ci please test |
… change to..." This reverts commit 7f8415b. The LLVM change this was intended for has since been cherry-picked to the current stable branch and dealt with differently on Swift main in swiftlang#81792.
With this PR changing some of the prefix mapping API's in llvm, some build errors are triggered in swift. I fixed the API usage to prevent those build errors so that the llvm PR can pass CI tests.
PR for cross-repo testing: swiftlang/llvm-project#10751