-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8357424: [JVMCI] Avoid incrementing decompilation count for hosted compiled nmethod #25356
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
base: master
Are you sure you want to change the base?
Conversation
👋 Welcome back yzheng! A progress list of the required criteria for merging this PR into |
@mur47x111 This change is no longer ready for integration - check the PR body for details. |
@mur47x111 The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
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 think there are two levels of counters that we might want to disable. We definitely want to stop deopts and recompilations from marking the method not compilable which the current change does. Additionally JVMCIRuntime::register_method will perform this logic if validate_compile_task_dependencies fails and I don't think we want that. I think the new The second level is to stop all counter updates in hosted compiles, for similar reasons. Those updates won't lead to disabling compilation but they will quickly lead to saturating of all the counters which is fairly pointless but probably benign. This would be done by setting |
@tkrodriguez by |
Yes. Any update to the MDO for hosted compiles doesn't seem useful I think. |
Added tag jdk-26+2 for changeset d7aa349
@@ -1947,6 +1947,11 @@ bool nmethod::is_maybe_on_stack() { | |||
void nmethod::inc_decompile_count() { | |||
if (!is_compiled_by_c2() && !is_compiled_by_jvmci()) return; | |||
// Could be gated by ProfileTraps, but do not bother... | |||
#if INCLUDE_JVMCI | |||
if (is_jvmci_hosted()) { |
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.
Someone (like me!) is going to see this code a while from now and try remember why the decompilation count is not being decremented for JVMCI hosted nmethods. I think it's worth adding a comment.
@@ -2363,6 +2363,11 @@ JRT_ENTRY(void, Deoptimization::uncommon_trap_inner(JavaThread* current, jint tr | |||
ShouldNotReachHere(); | |||
} | |||
|
|||
#if INCLUDE_JVMCI | |||
if (nm->is_jvmci_hosted()) { |
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.
A comment here will probably be helpful as well.
Hosted Truffle compilations are installed on the OptimizedCallTarget#profiledPERoot method. Any deoptimization contributes to its decompile count, which can easily exceed the PerMethodRecompilationCutoff threshold, permanently preventing highest tier compilation on this method. This PR exempts hosted compilations from this cutoff by ensuring their decompile count is not incremented for hosted compiled nmethods.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25356/head:pull/25356
$ git checkout pull/25356
Update a local copy of the PR:
$ git checkout pull/25356
$ git pull https://git.openjdk.org/jdk.git pull/25356/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 25356
View PR using the GUI difftool:
$ git pr show -t 25356
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25356.diff
Using Webrev
Link to Webrev Comment