-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8317677: Specialize Vtablestubs::entry_for() for VtableBlob #16099
8317677: Specialize Vtablestubs::entry_for() for VtableBlob #16099
Conversation
👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into |
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.
Nice improvement, looks good to me.
@tschatzl 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 69 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 |
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.
Thanks @TobiHartmann @vnkozlov for your reviews |
Going to push as commit 1082c0e.
Your commit was automatically rebased without conflicts. |
Hi all,
please review this change that specializes the call to
Vtablestubs::entry_for
for vtable blob.This kind of code blobs must always be in the
Vtablestubs
table (they are only created by theVtablestubs
class), so trying to find that stub there using it is unnecessary. For verification I added an assert that verifies it's found.Given that
Vtablestubs::entry_point()
would take a lock this removal of the lock results in a large speedup (https://bugs.openjdk.org/browse/JDK-8317527) in MT situations and is an even better change than that mentioned CR - and also worth the extra code (I did not retest performance since theVtablestubs
table lookup should be fairly fast).Fwiw, the first commit contains a different variant of this change, keeping the decision out of
Vtablestubs
, but I liked the current one better for it encapsulating that decision more. I am fine with reverting the second commit.Testing: tier1-7, gha, stress testing
Thanks,
Thomas
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16099/head:pull/16099
$ git checkout pull/16099
Update a local copy of the PR:
$ git checkout pull/16099
$ git pull https://git.openjdk.org/jdk.git pull/16099/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16099
View PR using the GUI difftool:
$ git pr show -t 16099
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16099.diff
Webrev
Link to Webrev Comment