8314951: VM build without C2 still fails after JDK-8313530

[DamonFool]

JDK-8313530 fixed the release VM build but the debug VM build would still fail.
This patch fix the debug VM build failure.
Thanks.

---

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-8314951: VM build without C2 still fails after JDK-8313530 (Bug - P2)

Reviewers

• Doug Simon (@dougxc - Reviewer)
• Vladimir Kozlov (@vnkozlov - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 15419

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

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

@DamonFool 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.

[mlbridge]

Webrevs

• 00: Full (2aea6e50)

[openjdk]

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

8314951: VM build without C2 still fails after JDK-8313530

Reviewed-by: dnsimon, kvn

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

• 2624324: 8219567: Name of first parameter of RandomAccessFile(String,String) is inconsistent
• 8e4240c: 8314850: SharedRuntime::handle_wrong_method() gets called too often when resolving Continuation.enter
• d9fc6b6: 8314759: VirtualThread.parkNanos timeout adjustment when pinned should be replaced
• acaab6f: 8306040: HttpResponseInputStream.available() returns 1 on empty stream

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.

[vnkozlov]

Good.

[DamonFool]

Thanks @dougxc and @vnkozlov for your review.
/integrate

[openjdk]

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

• 2624324: 8219567: Name of first parameter of RandomAccessFile(String,String) is inconsistent
• 8e4240c: 8314850: SharedRuntime::handle_wrong_method() gets called too often when resolving Continuation.enter
• d9fc6b6: 8314759: VirtualThread.parkNanos timeout adjustment when pinned should be replaced
• acaab6f: 8306040: HttpResponseInputStream.available() returns 1 on empty stream

Your commit was automatically rebased without conflicts.

[openjdk]

@DamonFool Pushed as commit d024059.

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