8330094: RISC-V: Save and restore FRM in the call stub

[zifeihan]

Hi, The same issue also exists in JDK21u. So I would like to backport JDK-8330094 to jdk21u-dev. With this change, we save and restore the default floating-point control state when we enter and leave Java code, ensuring that we are still Java compatible if we're called via the JNI invocation interface with a weird FP control state. RISC-V specific change, risk is low.
The backport is not clean because jdk21u-dev has no JDK-8321021

Testing

• Run tier1-3 tests on SOPHON SG2042 (release)

---

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-8330094 needs maintainer approval

Issue

• JDK-8330094: RISC-V: Save and restore FRM in the call stub (Enhancement - P4 - Approved)

Reviewers

• Fei Yang (@RealFYang - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 545

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

Using diff file

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

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:

8330094: RISC-V: Save and restore FRM in the call stub

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

• 3bb8eee: 8317809: Insertion of free code blobs into code cache can be very slow during class unloading
• a4d8d06: 8328744: Parallel: Parallel GC throws OOM before heap is fully expanded
• 87d5da4: 8328822: C2: "negative trip count?" assert failure in profile predicate code
• 3892078: 8324121: SIGFPE in PhaseIdealLoop::extract_long_range_checks
• 3ab3f52: 8326974: ODR violation in macroAssembler_aarch64.cpp
• 5d5c678: 8319713: Parallel: Remove PSAdaptiveSizePolicy::should_full_GC
• 56a9090: 8312014: [s390x] TestSigInfoInHsErrFile.java Failure
• c922c50: 8322962: Upcall stub might go undetected when freezing frames
• cbd30c9: 8325095: C2: bailout message broken: ResourceArea allocated string used after free
• 75ac9e8: 8328168: Epsilon: Premature OOM when allocating object larger than uncommitted heap size
• ... and 34 more: https://git.openjdk.org/jdk21u-dev/compare/7c6379146e3b5c5625ff25f1585d3d14d778ed70...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.

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 (768909ff)

[RealFYang]

LGTM.

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

[jerboaa]

/approve yes

[openjdk]

@jerboaa
8330094: The approval request has been approved.

[zifeihan]

@RealFYang @jerboaa : Thanks for the review.
/integrate

[openjdk]

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

[RealFYang]

/sponsor

[openjdk]

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

• 3bb8eee: 8317809: Insertion of free code blobs into code cache can be very slow during class unloading
• a4d8d06: 8328744: Parallel: Parallel GC throws OOM before heap is fully expanded
• 87d5da4: 8328822: C2: "negative trip count?" assert failure in profile predicate code
• 3892078: 8324121: SIGFPE in PhaseIdealLoop::extract_long_range_checks
• 3ab3f52: 8326974: ODR violation in macroAssembler_aarch64.cpp
• 5d5c678: 8319713: Parallel: Remove PSAdaptiveSizePolicy::should_full_GC
• 56a9090: 8312014: [s390x] TestSigInfoInHsErrFile.java Failure
• c922c50: 8322962: Upcall stub might go undetected when freezing frames
• cbd30c9: 8325095: C2: bailout message broken: ResourceArea allocated string used after free
• 75ac9e8: 8328168: Epsilon: Premature OOM when allocating object larger than uncommitted heap size
• ... and 34 more: https://git.openjdk.org/jdk21u-dev/compare/7c6379146e3b5c5625ff25f1585d3d14d778ed70...master

Your commit was automatically rebased without conflicts.

[openjdk]

@RealFYang @zifeihan Pushed as commit 835d016.

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