-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8286829: Shenandoah: fix Shenandoah Loom support #8924
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
Conversation
|
👋 Welcome back zgu! A progress list of the required criteria for merging this PR into |
|
@zhengyu123 The following labels 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 lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
|
|
||
| heap->set_concurrent_mark_in_progress(true); | ||
|
|
||
| _mark.start_mark(); |
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.
Style: call start_mark() here maybe? Matches the use of end_mark() elsewhere.
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.
Okay. I am award of asymmetry, but not sure this is better.
shipilev
left a comment
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.
I am okay with most of it, but still concerned with the injecting new code into hot marking loops.
shipilev
left a comment
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.
I still have a question: now that closures drop do_metadata, does that mean we always traverse metadata now? Which means we can remove half of the closures? For example, ShenandoahMarkUpdateRefsClosure and ShenandoahMarkUpdateRefsMetadataClosure are pretty much the same, right? We can leave ShenandoahMarkUpdateRefsClosure only then?
Yes, we always walk metadata now. And right, I need to look into duplicated closures. But can we do that in separate CR? Another round of tests going to take a couple of days, and I want to get this in before RDP1. Thanks. |
shipilev
left a comment
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.
All right then!
|
@zhengyu123 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 99 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, @shipilev |
|
/integrate |
|
Going to push as commit 239ac2a.
Your commit was automatically rebased without conflicts. |
|
@zhengyu123 Pushed as commit 239ac2a. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review the patch that fixes Loom support in Shenandoah GC.
Test:
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/8924/head:pull/8924$ git checkout pull/8924Update a local copy of the PR:
$ git checkout pull/8924$ git pull https://git.openjdk.java.net/jdk pull/8924/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 8924View PR using the GUI difftool:
$ git pr show -t 8924Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/8924.diff