This is the Java code which uses the new hook placed in hotspot under this same
bug.
http://cr.openjdk.java.net/~jrose/6939224/jdk-webrev.00/
-- John
___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
There is no up-call. The JVM just tail-calls an adapter previously prepared by
the JDK runtime. So the interpreter has no special paths other than the slow
path with the tail call.
I think your implementation put the adapter on a method header. I put it on the
method type family (the form).
6939224: MethodHandle.invokeGeneric needs to perform the correct set of
conversions
Until now, the HotSpot JVM has conflated invokeExact with invokeGeneric. These
changes, combined with forthcoming JDK runtime support changes, provide a hook
for the JVM to perform on-the-fly argument
