Implement JIT constant provenance graph

[jdmpapin]

See the doxygen for ConstProvenanceGraph in J9ConstProvenanceGraph.hpp.

The type is essentially unused for the moment. A follow-up change will populate the graph with edges. After that, the implementation of const refs will include the necessary graph search.

[jdmpapin]

@0xdaryl, could you please review?

[jdmpapin]

I've separated the addEdge() calls into a follow-up change because unfortunately a few of them will be in existing J9_PROJECT_SPECIFIC sections in OMR, and I don't want the OMR change to need to block on review of all of the addEdge() calls in OpenJ9.

[0xdaryl]

Perhaps this will be apparent when we see you put this graph into action, but will the graph population occur in a single "phase" (not sure that's the right word)? I'm asking mainly because of the tracing code. If the graph is populated in a single "phase" then the tracing output makes sense. But if it is intermixed with other analyses then there isn't anything remarkable about each tracing line to indicate its coming from provenance graph building.

[0xdaryl]

sp. anonymous

[jdmpapin]

fixed

[jdmpapin]

The graph won't be populated all at once, no. However, all output for a given call to addEdge() will be together, from the initial Const provenance: add edge: ... -> ... to the final accept edge or ignore redundant edge. Here's an example of how it looks in the midst of other output:

...
Inliner: CallSite Before finding call Targets
<callSite>
	_CallerResolvedMethod = 00007F38D42D6918	_callNodeTreeTop = 00007F38B1250508	_parent = 00007F38B12048F0	_callNode = 00007F38B12048A0
	_interfaceMethod = 00007F38B12502C0	_receiverClass = 0000000000000000	_vftSlot = 0	_cpIndex = 70
	_initialCalleeMethod = 0000000000000000	_initialCalleeSymbol = 0000000000000000	_bcInfo = 00007F38D42D25D8	_byteCodeIndex = 3	_isIndirectCall = 1
	_isInterface = 1	numtargets() = 0	 failureReason = 0 InlineableTarget
	 CALLER signature from method = UnloadableMain.go(LI;)V

</callSite>
Const provenance: add edge: class 00000000001DA900 X -> method 00007F38D03F0080 X.inlineCallee()V
    class 00000000001DA900 X is defined by class loader 00007F38D012ACD8
    method 00007F38D03F0080 X.inlineCallee()V is defined by class 00000000001DA900 X
    class 00000000001DA900 X is defined by class loader 00007F38D012ACD8
    ignore redundant edge: class loader 00007F38D012ACD8 -> class loader 00007F38D012ACD8
Found a Single Interface Implementer with Resolved Method 0x7f38b1271a98 for callsite 0x7f38d42d2570
RetainedMethodSet 00007F38B1271CD0: created with parent=00007F38B12717D0, method=00007F38D03F0080 X.inlineCallee()V in class 00000000001DA900
...

The trace output from the various overloads of place() will also appear in the graph search (if traceConstProvenance is enabled), which looks like this:

search graph from bond method 00007F38D03F0080 X.inlineCallee()V
    method 00007F38D03F0080 X.inlineCallee()V is defined by class 00000000001DA900 X
    class 00000000001DA900 X is defined by class loader 00007F38D012ACD8
  reachable: class loader 00007F38D012ACD8
  reachable: obj1
  reachable: obj2
  reachable: obj3

[0xdaryl]

Jenkins compile all jdk21

Only building rather than running tests since this isn't hooked up yet.

[jdmpapin]

Builds have succeeded