8263030: Remove Shenandoah leftovers from ReferenceProcessor

[rkennke]

Shenandoah is no longer using the shared ReferenceProcessor. We can remove remaining Shenandoah leftovers there.

Testing:

• hotspot_gc_shenandoah
• hotspot_gc

---

Progress

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

Issue

• JDK-8263030: Remove Shenandoah leftovers from ReferenceProcessor

Reviewers

• Zhengyu Gu (@zhengyu123 - Reviewer)

Download

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

[bridgekeeper]

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

@rkennke 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 (e2dc8ea)

[zhengyu123]

Looks good and trivial

[openjdk]

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

8263030: Remove Shenandoah leftovers from ReferenceProcessor

Reviewed-by: zgu

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 1 new commit pushed to the master branch:

• a777e82: 8254717: isAssignableFrom checks in KeyFactorySpi.engineGetKeySpec appear to be backwards

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.

[rkennke]

/integrate

[openjdk]

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

• 222a17e: 8262122: [TESTBUG] Shenandoah-specific variant of TestReferenceRefersTo
• a777e82: 8254717: isAssignableFrom checks in KeyFactorySpi.engineGetKeySpec appear to be backwards

Your commit was automatically rebased without conflicts.

Pushed as commit ef5e13d.

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