8322503: Shenandoah: Clarify gc state usage

[earthling-amzn]

Clean backport. This is a follow up to https://bugs.openjdk.org/browse/JDK-8321815, which renames methods and changes comments and adds an assert for improved readability.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8322503 needs maintainer approval

Issue

• JDK-8322503: Shenandoah: Clarify gc state usage (Enhancement - P4 - Approved)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk22u.git pull/101/head:pull/101
$ git checkout pull/101

Update a local copy of the PR:
$ git checkout pull/101
$ git pull https://git.openjdk.org/jdk22u.git pull/101/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 101

View PR using the GUI difftool:
$ git pr show -t 101

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk22u/pull/101.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back wkemper! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@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:

8322503: Shenandoah: Clarify gc state usage

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

⚠️ @earthling-amzn This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[mlbridge]

Webrevs

• 00: Full (13c9a6c7)

[earthling-amzn]

/approval request This is a follow up to JDK-8321815. It renames methods, improves comments, and adds an assert. I believe the risk is low. I also believe these GHA failures are unrelated to this change.

[openjdk]

@earthling-amzn
8322503: The approval request has been created successfully.

[earthling-amzn]

/integrate

[openjdk]

@earthling-amzn
Your change (at version 13c9a6c) is now ready to be sponsored by a Committer.

[shipilev]

/sponsor

[openjdk]

Going to push as commit afce5e6.
Since your change was applied there have been 2 commits pushed to the master branch:

• 6c2eefc: 8326529: JFR: Test for CompilerCompile events fails due to time out
• 2ec72f9: 8312383: Log X509ExtendedKeyManager implementation class name in TLS/SSL connection

Your commit was automatically rebased without conflicts.

[openjdk]

@shipilev @earthling-amzn Pushed as commit afce5e6.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.