-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Type checker] Keep the type checker alive as long as the ASTContext is. #19825
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
Merged
DougGregor
merged 4 commits into
swiftlang:master
from
DougGregor:immortal-type-checker
Oct 11, 2018
Merged
[Type checker] Keep the type checker alive as long as the ASTContext is. #19825
DougGregor
merged 4 commits into
swiftlang:master
from
DougGregor:immortal-type-checker
Oct 11, 2018
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
Doing this relies on type checker state getting wiped out in between SIL declarations, which is odd.
It is possible for the SIL optimizers, IRGen, etc. to request information from the AST that only the type checker can provide, but the type checker is typically torn down after the “type checking” phase. This can lead to various crashes late in the compilation cycle. Keep the type checker instance around as long as the ASTContext is alive or until someone asks for it to be destroyed. Fixes SR-285 / rdar://problem/23677338.
@swift-ci please test |
@swift-ci please test source compatibility |
@swift-ci please smoke test compiler performance |
Build failed |
@swift-ci please smoke test |
1 similar comment
@swift-ci please smoke test |
+1! |
slavapestov
added a commit
to slavapestov/swift
that referenced
this pull request
Dec 4, 2018
I believe this was fixed by swiftlang#19825, but this specific case with bitfield accessors is tricky so let's test it explicity.
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.
It is possible for the SIL optimizers, IRGen, etc. to request information
from the AST that only the type checker can provide, but the type checker
is typically torn down after the “type checking” phase. This can lead to
various crashes late in the compilation cycle.
Keep the type checker instance around as long as the ASTContext is alive
or until someone asks for it to be destroyed.
Fixes SR-285 / rdar://problem/23677338.