-
Notifications
You must be signed in to change notification settings - Fork 253
8274795: AArch64: avoid spilling and restoring r18 in macro assembler #744
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 burban! A progress list of the required criteria for merging this PR into |
|
This backport pull request has now been updated with issue from the original commit. |
|
@lewurm This change now passes all automated pre-integration checks. 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 46 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. 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 (@theRealAph) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
/integrate |
|
/sponsor |
|
Going to push as commit b5cae57.
Your commit was automatically rebased without conflicts. |
|
@VladimirKempik @lewurm Pushed as commit b5cae57. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
|
Thank you Andrew, Goetz and Vladimir! |
r18should not be used as it is reserved as platform register. Linux is fine with userspace using it, but Windows and also recently macOS (#301 (comment) ) are actually using it on the kernel side.The macro assembler uses the bit pattern
0x7fff_ffff(==r0-r30) to specify which registers to spill. While spillingr18is fine (e.g. for a register dump), we should never restore it.Tested tier1 on Linux/AArch64 and macOS/AArch64 (the latter on top of the current patches from openjdk/aarch64-port#14 ).
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u-dev pull/744/head:pull/744$ git checkout pull/744Update a local copy of the PR:
$ git checkout pull/744$ git pull https://git.openjdk.java.net/jdk11u-dev pull/744/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 744View PR using the GUI difftool:
$ git pr show -t 744Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u-dev/pull/744.diff