-
Notifications
You must be signed in to change notification settings - Fork 199
Pass the canonical SDK name to the frontend for swiftmodule checking #838
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 Please test |
Could you please (1) update |
@nkcsgexi How can we check if a flag is supported by the compiler? |
Nevermind, there's a |
Right, it's especially necessary when we are using one single driver instance to orchestrate multiple compilers. |
196c26a
to
a19861b
Compare
Adding commits for the suggested changes. @swift-ci Please test |
+1 nice addition |
@swift-ci Please test |
The frontend will use this information to control which swiftmodule file can be loaded according to the SDK in use. Swiftmodule files should only be used in the context of the SDK used to create them. This will catch issues with roots and other configuration problems. rdar://83104265
Other SDK sanity checks have landed. I believe it's time to merge this one. @swift-ci Please test |
Pass the canonical SDK name to the frontend for it to control which swiftmodule file can be loaded according to the SDK in use. Swiftmodule files should only be used in the context of the SDK used to create them. This will catch issues with roots and other similar configuration problems.
rdar://83104265
Related compiler-side PR: swiftlang/swift#37768