8387381: RISC-V: assert failed with fastdebug build on systems with different core types

[zifeihan]

Hi, this patch is a backport of openjdk/jdk#31717. this is a risc-v specific change, risk is low.
Because the order of these code changes does not match the order of the mainline code, so the patch is not clean.

Testing

• fastdebug build on SpacemiT Key Stone K3

---

• I confirm that I make this contribution in accordance with the OpenJDK Interim AI Policy.

---

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
• JDK-8387381 needs maintainer approval

Issue

• JDK-8387381: RISC-V: assert failed with fastdebug build on systems with different core types (Bug - P4 - Approved)

Reviewers

• Fei Yang (@RealFYang - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk25u-dev.git pull/653/head:pull/653
$ git checkout pull/653

Update a local copy of the PR:
$ git checkout pull/653
$ git pull https://git.openjdk.org/jdk25u-dev.git pull/653/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 653

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk25u-dev/pull/653.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8387381: RISC-V: assert failed with fastdebug build on systems with different core types

Reviewed-by: fyang

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@RealFYang) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 00: Full (e86c716e)

[RealFYang]

Thanks.

[openjdk]

⚠️ @zifeihan This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[zifeihan]

/approval request
Same issue is there in jdk25u-dev repo. This is a RISC-V specific change.
Verified by fastdebug build on on SpacemiT Key Stone K3

[openjdk]

@zifeihan
8387381: The approval request has been created successfully.

[zifeihan]

@RealFYang Thanks for the review.
/integrate

[openjdk]

@zifeihan
Your change (at version e86c716) is now ready to be sponsored by a Committer.

[RealFYang]

/sponsor

[openjdk]

Going to push as commit 137b05b.

[openjdk]

@RealFYang @zifeihan Pushed as commit 137b05b.

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