-
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
8314329: AgeTable: add is_clear() & allocation spec, and relax assert to allow use of 0-index slot #17470
Conversation
to allow use of 0-index slot
👋 Welcome back ysr! A progress list of the required criteria for merging this PR into |
@ysramakrishna This issue is referenced in the PR title - it will now be updated. |
@ysramakrishna Setting summary to:
|
@ysramakrishna The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
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.
Consider a minor optimization for is_clear
test.
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
Thanks @earthling-amzn & @kdnilsen! Could I please also have one of the G1 folk look over this and approve as a formal Reviewer, so I can push the change; may be @tschatzl or @stefank or @albertnetymk et al. Thanks! |
PRODUCT_RETURN0 for is_clear().
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.
Thanks for the revision. I guess the new API can be const
.
@ysramakrishna 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 43 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 |
/summary AgeTable changes:
|
@ysramakrishna Updating existing summary to:
|
Thanks for your reviews! /integrate |
Going to push as commit df370d7.
Your commit was automatically rebased without conflicts. |
@ysramakrishna Pushed as commit df370d7. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
/issue JDK-8314329
I'd like to propose the following changes to the AgeTable (motivated by the uses in generational shenandoah):
/summary
is_clear()
method that checks whether the age table has only zero entriesTesting:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17470/head:pull/17470
$ git checkout pull/17470
Update a local copy of the PR:
$ git checkout pull/17470
$ git pull https://git.openjdk.org/jdk.git pull/17470/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17470
View PR using the GUI difftool:
$ git pr show -t 17470
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17470.diff
Webrev
Link to Webrev Comment