-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8340456: Reduce overhead of proxying Object methods in ProxyGenerator #21090
Conversation
👋 Welcome back redestad! A progress list of the required criteria for merging this PR into |
@cl4es 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 9 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
if (cl == Object.class) { | ||
cob.ldc(objectCE); | ||
} else { | ||
cob.ldc(cl.getName()) |
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.
This Class.forName
is only necessary in a very small number of cases, namely when the overridden interface method has an unaccessible parameter type, usually a package-private type not accessible to the implementing class. Maybe we can always directly ldc if the class is public
.
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.
Yeah, I'm just not sure what rules are quite right here. Wouldn't want to inadvertently regress this again, and not sure we have tests for all eventualities, so I started this off with the most conservative yet most beneficial improvement.
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.
Replacing Class.forName with ldc or even condy is an esoteric topic. We can dive into that later and pick up the obvious gains.
Thanks! /integrate |
Going to push as commit a50440f.
Your commit was automatically rebased without conflicts. |
This PR changes proxy code gen to avoid generating
Class.forName("java.lang.Object")
, instead emitting an ldc for the class literal,ldc(CD_Object)
, java code equivalentObject.class
.More types could profitably use
ldc(ClassDesc/-Entry)
, taking cues fromInvokerBytecodeGenerator.isStaticallyInvocable
, but just addressing theObject
methods gets rid of mostClass.forName
emits. It's not terribly important for throughput performance since these are called in the generatedclinit
, so getting a quick win with few additional checks is a good starting point.Added a few unrelated minor refactors/improvements, guided by diagnostic runs of the now fixed microbenchmark.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/21090/head:pull/21090
$ git checkout pull/21090
Update a local copy of the PR:
$ git checkout pull/21090
$ git pull https://git.openjdk.org/jdk.git pull/21090/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 21090
View PR using the GUI difftool:
$ git pr show -t 21090
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/21090.diff
Webrev
Link to Webrev Comment