Modifying graph to include InvokeNode

[Christophe Dubach]

> An invoke node (that doesn't get inlined) in method A that calls method B will result in a call in the generated code. During execution of B, something may happen to invalidate an assumption made when compiling A (e.g., class loading invalidating a class hierarchy speculation). This means A is now invalid and needs to be deoptimized upon return from B. In the current system, we rely on HotSpot's deoptimization infrastructure to continue execution at the return site of A in the interpreter. HotSpot only (currently) supports deoptimize-on-return for call sites that have the BCI of an invoke bytecode.
Thank you for the clarification, I think I see the problem.

Is there a way we could add a new invokeNode in the graph and then force 
it to get inlined straight-away?

-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.