-
Notifications
You must be signed in to change notification settings - Fork 233
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
Simplify G1CodeBlobClosure #112
Conversation
👋 Welcome back stefank! A progress list of the required criteria for merging this PR into |
@stefank 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 9 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 As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@fisk) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
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 looking into this - that change has been one of the stranger to me as well.
Looks good.
Thanks for reviewing! |
@stefank Integration of this pull request has been deferred and may be completed by any project committer using the /integrate pull request command. |
/integrate |
/sponsor |
Going to push as commit 61d79b2.
Your commit was automatically rebased without conflicts. |
There's no need to introduce a new _keepalive_is_strong property in the G1CodeBlobClosure. The existing _strong is set to true when the evacuation participates in the marking of the old gen, which is when we need to mark the nmethods as "maybe on continuation". The name _strong in this context is not great and it doesn't convey the actual meaning. Maybe something for a future G1 cleanup.
Progress
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/loom pull/112/head:pull/112
$ git checkout pull/112
Update a local copy of the PR:
$ git checkout pull/112
$ git pull https://git.openjdk.java.net/loom pull/112/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 112
View PR using the GUI difftool:
$ git pr show -t 112
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/loom/pull/112.diff