-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8329628: Additional changes after JDK-8329332 #18665
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 kvn! A progress list of the required criteria for merging this PR into |
|
@vnkozlov 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 47 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 |
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.
Looks good. I've added two suggestions. You can choose to make them, handle them as separate issues, or just ignore them. :)
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.
I was never a fan of the CompiledMethod_lock name, as it is quite general but only protects a very specific thing: the state. With the NMethod_lock it gets slightly more awkward since the concurrent GCs already have an "nmethod lock" in the GC data of nmethods. Could this lock be called NMethodState_lock instead, to more clearly describe what exactly it is about nmethods that it guards?
|
I did all suggested changes. |
|
/integrate |
|
Going to push as commit 6736792.
Your commit was automatically rebased without conflicts. |
Additional clean up based on comments (mostly Stefan's) during reviews for JDK-8329332: Remove CompiledMethod and CodeBlobLayout classes.
CompiledMethod_locktoNMethod_lock. (I decided to not change JVMTI'sCompiledMethod[Load|Unload]names).NMethodIterator::all_blobstoNMethodIterator::all.get_deopt_original_pc()method fromnmethodtoframeclass.CodeCache::find_nmethod()to previous functionality to allow returnnullptrand be consistent withfind_blob().(nmethod*)casts.for (CodeHeap* heap : *_nmethod_heaps)inCodeCache::nmethod_count()(it was @stefank suggestion, I don't know how this C++ magic works). I verified it running with-XX:+PrintNMethodStatistics.Testing tier1-3,xcomp,stress
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18665/head:pull/18665$ git checkout pull/18665Update a local copy of the PR:
$ git checkout pull/18665$ git pull https://git.openjdk.org/jdk.git pull/18665/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18665View PR using the GUI difftool:
$ git pr show -t 18665Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18665.diff
Webrev
Link to Webrev Comment