-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8322503: Shenandoah: Clarify gc state usage #17163
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
8322503: Shenandoah: Clarify gc state usage #17163
Conversation
…e thread local copy of gc state
|
👋 Welcome back wkemper! A progress list of the required criteria for merging this PR into |
|
@earthling-amzn 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
|
| void set_gc_state(uint mask, bool value); | ||
|
|
||
| public: | ||
| char gc_state() const; | ||
| void set_gc_state_all_threads(); | ||
| bool has_gc_state_changed() { return _gc_state_changed; } | ||
| void propagate_gc_state_to_java_threads(); | ||
| bool has_gc_state_changed() const { return _gc_state_changed; } |
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.
The name changes per @shipilev look good. If we have a sentence of documentation in the header file for each of these methods, that makes things even clearer (and is not subject to limitations on the length of the method name :-)
|
@earthling-amzn 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 16 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. 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 (@ysramakrishna, @lgxbslgx) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
/integrate Added comments to new methods and synced up with tip to see if it addresses GHA build failure on macosx. |
|
@earthling-amzn |
lgxbslgx
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.
Looks good.
|
/sponsor |
|
Going to push as commit 51238c4.
Your commit was automatically rebased without conflicts. |
|
@ysramakrishna @earthling-amzn Pushed as commit 51238c4. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This is a follow up to #17112.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17163/head:pull/17163$ git checkout pull/17163Update a local copy of the PR:
$ git checkout pull/17163$ git pull https://git.openjdk.org/jdk.git pull/17163/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17163View PR using the GUI difftool:
$ git pr show -t 17163Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17163.diff
Webrev
Link to Webrev Comment