Skip to content

Commit 01824c4

Browse files
committed
Check for Explicit Compilation in the replenishInvocationCount() Assertion
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 eclipse-openj9#15472 Signed-off-by: Luke Li <[email protected]>
1 parent 775e962 commit 01824c4

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

runtime/compiler/control/CompilationThread.cpp

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11955,7 +11955,9 @@ TR::CompilationInfo::replenishInvocationCount(J9Method *method, TR::Compilation
1195511955
}
1195611956
else
1195711957
{
11958-
TR_ASSERT(false, "Unexpected value for method->extra = %p (method=%p)\n", TR::CompilationInfo::getJ9MethodExtra(method), method);
11958+
TR_ASSERT(comp->getOptimizationPlan()->isExplicitCompilation(),
11959+
"Unexpected value for method->extra = %p (method=%p)\n",
11960+
TR::CompilationInfo::getJ9MethodExtra(method), method);
1195911961
}
1196011962
}
1196111963

0 commit comments

Comments
 (0)