Skip to content

Commit

Permalink
Check for Explicit Compilation in the replenishInvocationCount() Asse…
Browse files Browse the repository at this point in the history
…rtion

replenishInvocationCount will only raise the assertion
failure for unexpected count value if the compilation was not set
as explicit, since the count value can be any positive integer
in that case.

Based on #15472

Signed-off-by: Luke Li <[email protected]>
  • Loading branch information
luke-li-2003 committed Jan 2, 2025
1 parent 775e962 commit 01824c4
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion runtime/compiler/control/CompilationThread.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -11955,7 +11955,9 @@ TR::CompilationInfo::replenishInvocationCount(J9Method *method, TR::Compilation
}
else
{
TR_ASSERT(false, "Unexpected value for method->extra = %p (method=%p)\n", TR::CompilationInfo::getJ9MethodExtra(method), method);
TR_ASSERT(comp->getOptimizationPlan()->isExplicitCompilation(),
"Unexpected value for method->extra = %p (method=%p)\n",
TR::CompilationInfo::getJ9MethodExtra(method), method);
}
}

Expand Down

0 comments on commit 01824c4

Please sign in to comment.