-
Notifications
You must be signed in to change notification settings - Fork 141
8372806: [lworld] x64: save bad values instead of rfp and lr above the extension space #1839
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 mchevalier! A progress list of the required criteria for merging this PR into |
|
@marc-chevalier 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 84 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 |
TobiHartmann
left a comment
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.
Nice comments! The changes look good to me.
|
/integrate Thanks for review! |
|
Going to push as commit 328cfbe.
Your commit was automatically rebased without conflicts. |
|
@marc-chevalier Pushed as commit 328cfbe. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
That's the x86 counterpart of JDK-8371993.
I've added some comments, using the offsets given in
frame_x86.hppto make sure to put the frame start at the right place. In particular, the frame start is 2 pointer sizes under the sender's sp:valhalla/src/hotspot/cpu/x86/frame_x86.hpp
Lines 61 to 62 in 3c41c2a
Unlike aarch64, with x64 we have only one copy of rbp. As with aarch64, I had to get rid of an assert that can't be checked anymore. A small price to pay.
Now, in debug, instead of
we have
I've kept the
pop r13to limit the difference of behavior between debug and product builds: both will overwriter13with the return address, whether it's a good idea or not.And at runtime, on my favorite
compiler/valhalla/inlinetypes/CorrectlyRestoreRfp.javaexample, instead of the stack:we have
I had to problem list some virtual thread tests, in the same fashion as for aarch64, as it used the wrong return address. The assert I had to remove was a sign that only one of the return address is updated in case of deopt, so only one of them is reliable. To help with that, I've added
frame::compiled_frame_detailslike for aarch64, that makes sure to do all the fixing internally.Thanks,
Marc
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/valhalla.git pull/1839/head:pull/1839$ git checkout pull/1839Update a local copy of the PR:
$ git checkout pull/1839$ git pull https://git.openjdk.org/valhalla.git pull/1839/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1839View PR using the GUI difftool:
$ git pr show -t 1839Using diff file
Download this PR as a diff file:
https://git.openjdk.org/valhalla/pull/1839.diff
Using Webrev
Link to Webrev Comment