SIL: Fix TypeExpansionContext() constructor to get the right DeclContext from a SILFunction #33428
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ext from a SILFunction Using the SILFunction's DeclContext produces the wrong result for the @main function, because it returns the ModuleDecl even in a non-WMO build. Instead, let's always just use SILModule::getAssociatedContext(), which also simplifies the code here. Fixes <rdar://problem/66791399>.
|
@swift-ci Please smoke test |
aschwaighofer
approved these changes
Aug 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using the SILFunction's DeclContext produces the wrong result for
the @main function, because it returns the ModuleDecl even in
a non-WMO build.
Instead, let's always just use SILModule::getAssociatedContext(),
which also simplifies the code here.
Fixes rdar://problem/66791399.