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
8297784: Optimize @Stable field for Method.isCallerSensitive #11422
8297784: Optimize @Stable field for Method.isCallerSensitive #11422
Conversation
👋 Welcome back shade! 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.
LGTM.
@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 20 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 |
/integrate |
Going to push as commit 9bbcb54.
Your commit was automatically rebased without conflicts. |
JDK-8271820 introduced the
@Stable private Boolean callerSensitive;
cache inMethod
. That field is essentially a tri-stateBoolean
that relies on itsnull
value to serve as "not initialized" value for@Stable
.This works well when the holder
Method
instance is constant: JIT compilers fold@Stable
well. But if such folding fails, we always dereference the full-blown reference to "boxed"Boolean
from the field on every access. We can instead do a more lean tri-state primitive field to improve that non-optimized case without sacrificing optimized case.I chose
byte
and-1
,0
,1
to let the fastpath encode well on most (all?) architectures.On adhoc benchmark like:
We have a minor improvement for non-const case, confirmed due to better
isCallerSensitive
access:Additional testing:
java/lang/reflect
tier1
,tier2
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11422/head:pull/11422
$ git checkout pull/11422
Update a local copy of the PR:
$ git checkout pull/11422
$ git pull https://git.openjdk.org/jdk pull/11422/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11422
View PR using the GUI difftool:
$ git pr show -t 11422
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11422.diff