-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8261842: Shenandoah: cleanup ShenandoahHeapRegionSet #2592
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
8261842: Shenandoah: cleanup ShenandoahHeapRegionSet #2592
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.
Ok!
|
@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 5 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
|
/integrate |
|
@shipilev Since your change was applied there have been 10 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit d195033. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
There are a couple of stale/unused methods in ShenandoahHeapRegionSet that we can eliminate instead of improving them, for example in JDK-8261838.
Additional testing:
hotspot_gc_shenandoahProgress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/2592/head:pull/2592$ git checkout pull/2592