-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8322954: Shenandoah: Convert evac-update closures asserts to rich asserts #17245
8322954: Shenandoah: Convert evac-update closures asserts to rich asserts #17245
Conversation
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
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.
LGTM
@shipilev This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 40 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
Thanks! /integrate |
Going to push as commit 700c25f.
Your commit was automatically rebased without conflicts. |
Over the years, we seem to have introduced new asserts that should really be the rich Shenandoah asserts. I looked around and found at least three places in evac-update closures.
We also do not need
_mark_context->is_marked(resolved)
inShenandoahEvacUpdateCleanupOopStorageRootsClosure
, because evac-ed objects are supposed to be after TAMS and thus implicitly marked.Additional testing:
hotspot_gc_shenandoah
tier{1,2,3}
with-XX:+UseShenandoahGC
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17245/head:pull/17245
$ git checkout pull/17245
Update a local copy of the PR:
$ git checkout pull/17245
$ git pull https://git.openjdk.org/jdk.git pull/17245/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17245
View PR using the GUI difftool:
$ git pr show -t 17245
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17245.diff
Webrev
Link to Webrev Comment