-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8353588: [REDO] DaCapo xalan performance with -XX:+UseObjectMonitorTable #24413
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
Conversation
|
👋 Welcome back rkennke! A progress list of the required criteria for merging this PR into |
|
@rkennke 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 4 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 |
Webrevs
|
coleenp
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.
@xmas92 had two choices in the CR but I like this one better because a few lines above it also clears the object_monitor_cache for UseObjectMonitorTable, and I don't like testing null pointers.
|
Also, I'll run this through our tier1-4 testing. |
coleenp
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.
Yes, I'll repost when testing is finished.
|
Our internal tier1-4 tests passed. |
xmas92
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.
Alright. I'll hope we can improve this mechanism to be less fragile and more obvious in the future.
The stack cache was always written to be for C2 and the CacheSetter was there to cover all the other places we construct these BasicLocks in case they appear in a C2 frame. Now we are using it bidirectionally in both enter and exit.
But this should work, and I know you are working on future improvements here @coleenp
Thanks for the fix @rkennke
|
Going to push as commit d894b78.
Your commit was automatically rebased without conflicts. |
Like #24098, but clears the BasicLock cache before calling inflate_and_enter().
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24413/head:pull/24413$ git checkout pull/24413Update a local copy of the PR:
$ git checkout pull/24413$ git pull https://git.openjdk.org/jdk.git pull/24413/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24413View PR using the GUI difftool:
$ git pr show -t 24413Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24413.diff
Using Webrev
Link to Webrev Comment