8357370: Export supported GCs in JVMCI

[rkennke]

I need a way to detect in JVMCI if Shenandoah GC is supported (that is, built-in) by HotSpot. I need it for Shenandoah, because some vendors don't build it, but for cleanliness the relevant preprocessor constants should be exported for all GCs.

Testing:

• build/test Shenandoah support oracle/graal#10904

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8357370: Export supported GCs in JVMCI (Enhancement - P4)

Reviewers

• Doug Simon (@dougxc - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25325

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25325.diff

Using Webrev

Link to Webrev Comment

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

8357370: Export supported GCs in JVMCI

Reviewed-by: dnsimon

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

• 62d155e: 8355230: Crash in fuzzer tests: assert(n != nullptr) failed: must not be null
• 277bb20: 8355094: Performance drop in auto-vectorized kernel due to split store
• e6750a5: 8357218: G1: Remove loop in G1CollectedHeap::try_collect_fullgc
• ... and 140 more: https://git.openjdk.org/jdk/compare/ab8c808ed8ebec4f70141ee31fbaf312fccf7fa4...master

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.

[openjdk]

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

• graal
• hotspot-compiler

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.

[dougxc]

Probably best to make the formatting consistent with how it's done for the JVM_ACC_* constants below (i.e., no alignment of values).

[mlbridge]

Webrevs

• 02: Full - Incremental (16d82e7b)
• 01: Full - Incremental (321a0940)
• 00: Full (7caef245)

[dougxc]

LGTM and trivial.

[rkennke]

Thanks!
/integrate

[openjdk]

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

• b8057cf: 8357436: Change jspawnhelper warning recommendation from VFORK to FORK
• 7c82e09: 8357048: RunTest variables should always be assigned
• 5f38d1b: 8357193: [VS 2022 17.14] Warning C5287 in debugInit.c: enum type mismatch during build
• ... and 154 more: https://git.openjdk.org/jdk/compare/ab8c808ed8ebec4f70141ee31fbaf312fccf7fa4...master

Your commit was automatically rebased without conflicts.

[openjdk]

@rkennke Pushed as commit 2c126f1.

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