-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Inherit -strict-implicit-module-context when build sub swiftinterface #66980
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
Inherit -strict-implicit-module-context when build sub swiftinterface #66980
Conversation
…ub swiftinterface
@Fushj89 could you please first file a PR with this change targeting |
@swift-ci test |
@artemcm I edit the PR description format. The PR is waiting for another approve, can you help find other reviewer to review it. |
@DougGregor Can you help review the PR |
@@ -1830,6 +1832,10 @@ InterfaceSubContextDelegateImpl::runInSubCompilerInstance(StringRef moduleName, | |||
// invocation. | |||
CompilerInvocation subInvocation = genericSubInvocation; | |||
|
|||
// save `StrictImplicitModuleContext` | |||
bool StrictImplicitModuleContext = | |||
subInvocation.getFrontendOptions().StrictImplicitModuleContext; |
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.
Why do we need to save and restore StrictImplicitModuleContext
here? It stands out from the rest of frontend options.
We are past taking changes of this nature in 5.9 for non-critical fixes, and are focusing on upcoming releases. This change made it to 5.10 so that will be the first release containing this change. Thank you @Fushj89! |
Cherry-pick of #67009
strict-implicit-module-context
flag which causes sub invocation build clang module in the swiftinterface failed.-strict-implicit-module-context
to swift-frontend