-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8353176: C1: x86 patching stub always calls Thread::current() #24291
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
8353176: C1: x86 patching stub always calls Thread::current() #24291
Conversation
|
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
|
@shipilev 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 17 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 |
|
Sample code density improvements: |
TheRealMDoerr
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.
LGTM.
vnkozlov
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.
Good.
iwanowww
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.
Looks good.
|
Thanks! I am in the middle of x86 C1 cleanups, but I believe this does not conflict with anything in flight. So I am integrating. /integrate |
|
Going to push as commit 6fbaa06.
Your commit was automatically rebased without conflicts. |
Noticed this while looking at compiled code density. In C1 PatchingStub code, we always perform a runtime call to
Thread::current(), even though we can rely onr15_threadto be available. This currently emits a huge sequence of instructions for register save/restore and the call itself.Current code calls to
MacroAssembler::get_thread(), which is always doing that slowpath. This kind of accident would be less likely / impossible once we cleanup uses ofMacroAssembler::get_thread()with JDK-8353174.Additional testing:
tier1tier1+-XX:TieredStopAtLevel=1allall+-XX:TieredStopAtLevel=1Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24291/head:pull/24291$ git checkout pull/24291Update a local copy of the PR:
$ git checkout pull/24291$ git pull https://git.openjdk.org/jdk.git pull/24291/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24291View PR using the GUI difftool:
$ git pr show -t 24291Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24291.diff
Using Webrev
Link to Webrev Comment