Generate ProfiledClassRecord for new classes only #4226
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
A ProfiledClassRecord for a class that has already been determined causes the validation process to choose arbitrarily from the classes that match the given class chain, and then to verify that this new choice agrees with the existing one. Eliminating the ProfiledClassRecord in this case saves space, and causes the validation process to behave as though it always makes the correct choice. Signed-off-by: Devin Papineau <devinmp@ca.ibm.com>
28 tasks
dsouzai
approved these changes
Jan 10, 2019
|
Jenkins test sanity xlinux,win,plinux jdk8,jdk11 |
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.
A
ProfiledClassRecordfor a class that has already been determined causes the validation process to choose arbitrarily from the classes that match the given class chain, and then to verify that this new choice agrees with the existing one. Eliminating theProfiledClassRecordin this case saves space, and causes the validation process to behave as though it always makes the correct choice.