-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Avoid classfile parsing of specialized variants just to unlink them #9549
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
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
Member
Author
|
Before: After: |
Since 8ae0fda, the specializion phase eagerly info transforms all of FunctionN and TupleN. This was done to let us turn off needless specialization info transforms (which incurs classfile parsing up the base classes looking for @specialized annotations) of types after the specialization tree transform is done. However, in combination with an old fix for scala/bug#5545, we end up parsing all of the class files of all the variants, just to unlink them in favour of the info-transformed types. I note that the test for scala/bug#5545 no longer crashes if the fix is removed. I have have not investigated the reason. This commit reworks the scala/bug#5545 to just unlink the stale symbols directly, rather than calling `.info` to parse them and do the same after noticing the ScalaRaw attribute.
08be401 to
f758d79
Compare
lrytz
approved these changes
Mar 24, 2021
Member
lrytz
left a comment
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.
👍
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.
Since 8ae0fda, the specializion phase eagerly info transforms
all of FunctionN and TupleN. This was done to let us turn off
needless specialization info transforms (which incurs classfile parsing
up the base classes looking for @specialized annotations) of types after
the specialization tree transform is done.
However, in combination with an old fix for scala/bug#5545, we end
up parsing all of the class files of all the variants, just to
unlink them in favour of the info-transformed types.
I note that the test for scala/bug#5545 no longer crashes if the fix
is removed. I have have not investigated the reason.
This commit reworks the scala/bug#5545 to just unlink the stale
symbols directly, rather than calling
.infoto parse them anddo the same after noticing the ScalaRaw attribute.