Stop registering class extend assumptions for HCR guards #15727
Merged
Conversation
This file contains 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
|
Please fix the copyright in CHTable.cpp |
Extending the defining class of an inlined method does not invalidate the bodies of methods defined by that class, which remain unchanged until/unless the class is actually redefined. It's possible for a guard merged with an HCR guard to require a class extend assumption for its (non-HCR) virtual guard semantics. In that case, execution will continue on and create the class extend assumption in exactly the same way as it would without the merged HCR guard.
jdmpapin
force-pushed
the
no-hcr-on-extend
branch
from
eea4343
to
2152a93
Compare
|
Updated the copyright header |
|
Jenkins test sanity all jdk17 |
0xdaryl
approved these changes
Aug 19, 2022
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.
Extending the defining class of an inlined method does not invalidate the bodies of methods defined by that class, which remain unchanged until/unless the class is actually redefined.
It's possible for a guard merged with an HCR guard to require a class extend assumption for its (non-HCR) virtual guard semantics. In that case, execution will continue on and create the class extend assumption in exactly the same way as it would without the merged HCR guard.