-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8319973: AArch64: Save and restore FPCR in the call stub #16637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
👋 Welcome back aph! A progress list of the required criteria for merging this PR into |
@theRealAph The following label will be automatically applied to this pull request:
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All looks good.
@theRealAph 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:
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 170 new commits pushed to the
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, one question inline.
@@ -141,7 +141,8 @@ class StubGenerator: public StubCodeGenerator { | |||
// [ return_from_Java ] <--- sp | |||
// [ argument word n ] | |||
// ... | |||
// -27 [ argument word 1 ] | |||
// -29 [ argument word 1 ] | |||
// -28 [ saved Floating-point Control Register ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the 1-word gap? Alignment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, exactly. AArch64 stack is 16-aligned, and this is enforced by hardware.
/integrate |
Going to push as commit 6e86904.
Your commit was automatically rebased without conflicts. |
@theRealAph Pushed as commit 6e86904. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
On AArch64 we don't save and restore the default floating-point control state when we enter and leave Java code. We really should, because if we're called via the JNI invocation interface with a weird FP control state we'll not be Java compatible.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16637/head:pull/16637
$ git checkout pull/16637
Update a local copy of the PR:
$ git checkout pull/16637
$ git pull https://git.openjdk.org/jdk.git pull/16637/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16637
View PR using the GUI difftool:
$ git pr show -t 16637
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16637.diff
Webrev
Link to Webrev Comment