8255036: Shenandoah: Reset GC state for root verifier

[zhengyu123]

Shenandoah has ShenandoahGCStateResetter to reset gc state for verifier to avoid triggering barriers inadvertently, root verifier should do the same.

Also, SH::_concurrent_weak_root_in_progress flag now has implication for native barrier, ShenandoahGCStateResetter should reset this flag too.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Testing

	Linux x32	Linux x64	Windows x64	macOS x64
Build	✔️ (1/1 passed)	✔️ (5/5 passed)	✔️ (2/2 passed)	✔️ (2/2 passed)
Test (tier1)		✔️ (9/9 passed)	⏳ (1/9 running)	✔️ (9/9 passed)

Issue

• JDK-8255036: Shenandoah: Reset GC state for root verifier

Reviewers

• Roman Kennke (@rkennke - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/jdk pull/781/head:pull/781
$ git checkout pull/781

[bridgekeeper]

👋 Welcome back zgu! 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]

@zhengyu123 The following labels will be automatically applied to this pull request:

• hotspot-gc
• shenandoah

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.

[mlbridge]

Webrevs

• 00: Full (622ed24)

[rkennke]

Looks good to me. I'd change the commit msg to begin with uppercase after Shenandoah: and form an imperative statement: "Shenandoah: Reset GC state for root verifier"

[openjdk]

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

8255036: Shenandoah: Reset GC state for root verifier

Reviewed-by: rkennke

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 2 new commits pushed to the master branch:

• 839f01d: 8242068: Signed JAR support for RSASSA-PSS and EdDSA
• e559bd2: 8254889: name_and_sig_as_C_string usages in frame coding without ResourceMark

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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 master branch, type /integrate in a new comment.

[zhengyu123]

/integrate

[openjdk]

@zhengyu123 Since your change was applied there have been 2 commits pushed to the master branch:

• 839f01d: 8242068: Signed JAR support for RSASSA-PSS and EdDSA
• e559bd2: 8254889: name_and_sig_as_C_string usages in frame coding without ResourceMark

Your commit was automatically rebased without conflicts.

Pushed as commit c9269bf.

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