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 eclipse-openj9/openj9#15472 Signed-off-by: Luke Li <[email protected]>
luke-li-2003 · Dec 31, 2024 · cd06d49 · cd06d49
1 parent 3ddaad3
commit cd06d49
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/compiler/control/OptimizationPlan.hpp b/compiler/control/OptimizationPlan.hpp
@@ -168,6 +168,9 @@ class TR_OptimizationPlan
    bool getDisableEDO() const { return _flags.testAny(DisableEDO); }
    void setDisableEDO(bool b) { _flags.set(DisableEDO, b); }
 
+   bool getIsCompileMethodAPI() const { return _flags.testAny(IsCompileMethodAPI); }
+   void setIsCompileMethodAPI(bool b) { _flags.set(IsCompileMethodAPI, b); }
+
    // --------------------------------------------------------------------------
    // GPU
    //
@@ -224,6 +227,7 @@ class TR_OptimizationPlan
       DowngradedDueToSamplingJProfiling=0x00400000, // Compilation was downgraded to cold just because we wanted to do JProfiling
       InducedByDLT            = 0x00800000, // Compilation that follows a DLT compilation
       DisableEDO              = 0x01000000, // Do not insert EDO profiling trees for this compilation
+      IsCompileMethodAPI      = 0x02000000, // plan created by TR_MethodEvent::CompileMethodAPI
    };
    private:
    TR_OptimizationPlan  *_next;       // to link events in the pool