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
8292878: x86: Make scratch register usage explicit in assembler code #10003
Conversation
👋 Welcome back vlivanov! A progress list of the required criteria for merging this PR into |
Webrevs
|
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.
I hope you did not do this all by hand ;)
Good.
@iwanowww 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 68 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 |
Accidentally, introduced a bug by turning some Reverted relevant chanages, plus made the scratch register argument required for Improved Also, applied a minor refactoring around |
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.
Still good.
Thanks for the review, Vladimir. @shipilev Aleksey, do you plan to look into x86_32-specific changes? Otherwise, I'll integrate the patch. |
Missed this comment, sorry. Are you looking for a similar change on x86_32-specific code? I believe x86_32 code does not use scratch registers (they are |
Thanks. Just wanted to hear from you since it affects x86_32 in a non-trivial way. |
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.
I think we are fine. tier1
and tier2
pass on x86_32.
Thanks, Aleksey. /integrate |
Going to push as commit 6e24827.
Your commit was automatically rebased without conflicts. |
Improve MacroAssembler API and make scratch register usages explicit at use sites.
Different parts of JVM have different assumptions about scratch registers and
implicit assumptions in MacroAssembler makes it harder to reason about the
correctness of generated code.
Most of scratch register usages relate to
AddressLiteral
on x86_64. In such case the argument is turned into a default one (withnoreg
as a default) and implementation asserts that scratch register should be provided when the address is not guaranteed to be always reachable.Otherwise, scratch register argument is required to be explicitly provided.
The only case left (mostly) intact is
call(AddressLiteral)
, but I switched it fromrscratch
(r10
) torax
.Testing:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10003/head:pull/10003
$ git checkout pull/10003
Update a local copy of the PR:
$ git checkout pull/10003
$ git pull https://git.openjdk.org/jdk pull/10003/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10003
View PR using the GUI difftool:
$ git pr show -t 10003
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10003.diff