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
8281744: x86: Use short jumps in TIG::set_vtos_entry_points #7463
Conversation
|
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.
Thanks
@shipilev 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 37 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.
|
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
Thanks for reviews! /integrate |
Going to push as commit 1870465.
Your commit was automatically rebased without conflicts. |
Performance in
-Xint
mode seems to be bottlenecked on the code size, rather than particular instruction hotspots, which means code density is important.There are forward branches in
TemplateInterpreterGenerator::set_vtos_entry_points
, which cannot be shortened byMacroAssembler
, unless we tell it specifically that the upcoming branch target would be within the 8-bit offset. Which it apparently is in this particular case, because there are just a handful ofpush
-es between the jump and its target. If a jump offset is more than 8 bits, the interpreter would catch fire just about everywhere, sinceset_vtos_entry_points
is used at every bytecode entry.fastdebug
builds assert the offset sanity directly.Current patch improves
SPECjvm2008
performance in-Xint
mode on Ryzen 7 5700G:There are other places in template interpreter where forward jumps can be short, I'll do them separately, since they are riskier and also less important.
Additional testing:
tier1
tier1
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/7463/head:pull/7463
$ git checkout pull/7463
Update a local copy of the PR:
$ git checkout pull/7463
$ git pull https://git.openjdk.java.net/jdk pull/7463/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 7463
View PR using the GUI difftool:
$ git pr show -t 7463
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/7463.diff