8256727: ZGC: Clean out dead code after JDK-8212879

[stefank]

There are some unused root processing functions after the JVMTI Tag Map was made concurrent. Clean them out.

---

Progress

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

Testing

	Linux aarch64	Linux arm	Linux ppc64le	Linux s390x	Linux x64	Linux x86	Windows x64	macOS x64
Build	✔️ (1/1 passed)	✔️ (1/1 passed)	✔️ (1/1 passed)	✔️ (1/1 passed)	✔️ (6/6 passed)	✔️ (2/2 passed)	✔️ (2/2 passed)	✔️ (2/2 passed)
Test (tier1)					✔️ (9/9 passed)	✔️ (9/9 passed)	✔️ (9/9 passed)	✔️ (9/9 passed)

Issue

• JDK-8256727: ZGC: Clean out dead code after JDK-8212879

Reviewers

• Per Liden (@pliden - Reviewer)

Download

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

[bridgekeeper]

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

@stefank The following label will be automatically applied to this pull request:

• hotspot-gc

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (a6f6611)

[pliden]

Looks good!

[openjdk]

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

8256727: ZGC: Clean out dead code after JDK-8212879

Reviewed-by: pliden

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

• eb35ade: 6232281: -XX:-UseLoopSafepoints causes assert(v_false,"Parse::remove_useless_nodes missed this node")
• a25fb03: 8256406: G1 x86 C1/Interpreter post write barrier always uses 32 bit to access variable sized PtrQueue::_index
• f576628: 8256633: Fix product build on Windows+Arm64
• 8e7a855: 8255526: Enable jcheck whitespace checking of build system files
• c45ab1a: 8256393: Github Actions build on Linux should define OS and GCC versions

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.

[stefank]

Thanks!
/integrate

[openjdk]

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

• eb35ade: 6232281: -XX:-UseLoopSafepoints causes assert(v_false,"Parse::remove_useless_nodes missed this node")
• a25fb03: 8256406: G1 x86 C1/Interpreter post write barrier always uses 32 bit to access variable sized PtrQueue::_index
• f576628: 8256633: Fix product build on Windows+Arm64
• 8e7a855: 8255526: Enable jcheck whitespace checking of build system files
• c45ab1a: 8256393: Github Actions build on Linux should define OS and GCC versions

Your commit was automatically rebased without conflicts.

Pushed as commit 10ba541.

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