Consider the compileMethod() API in replenishInvocationCount() Assertion

Add a flag in the optimization plan for compilations triggered by the compileMethod API, which can have the invocation count be any positive integer; replenishInvocationCount will not raise the assertion failure for unexpected count value. Based on #15472 Signed-off-by: Luke Li <[email protected]>
eclipse-openj9 · Jan 2, 2025 · 77067cc · 77067cc
1 parent 775e962
commit 77067cc
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/runtime/compiler/control/CompilationThread.cpp b/runtime/compiler/control/CompilationThread.cpp
@@ -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);
       }
    }