Fixes for -XX:+ClassRelationshipVerifier implementation #7148
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
Only set the runtime flag for -XX:+ClassRelationshipVerifier if -Xfuture is not enabled. Signed-off-by: Sharon Wang <sharon-wang-cpsc@outlook.com>
Intermittent test failures were occurring due to the use of `initializationLock` in the exception check. If gc occurs and the lock is not updated (pushed/popped properly), then the lock may be bogus. `setInitStatus()` would then attempt to use the bogus lock, causing a segmentation fault. Signed-off-by: Sharon Wang <sharon-wang-cpsc@outlook.com>
|
jenkins test sanity,extended xlinux,win jdk11 |
1 similar comment
|
jenkins test sanity,extended xlinux,win jdk11 |
pshipton
approved these changes
Sep 19, 2019
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.
Fixes: #7140
Remove redundant exception check causing intermittent failures
initializationLockin the exception check. If gc occurs and the lock is not updated (pushed/popped properly), then the lock may be bogus.setInitStatus()would then attempt to use the bogus lock, causing a segmentation fault.Set class relationships runtime flag only if -Xfuture is not used
Related to #7089