The document deconstructs the current implementation of
MethodHandle in OpenJDK.
Note: the Java documentation of
MethodHandle provides a more detailed and thorough description of interoperable
MethodHandles are cunning:
Blackadder: I have come up with a plan so cunning you could stick a tail on it and call it a weasel.
The general philosophy is to leverage a few key intrinsic mechanisms of HotSpot, perform most of the heavy lifting in Java code, and let the runtime compiler "have-at-it" and inline that code.
This section deconstructs how exact invocation of MethodHandles are compiled, linked and executed using a specific example of setting the value of a non-static field. Examples of byte code and inlining traces are obtained by compiling and executing a
Despite the name a
Methodhandle can reference an underlying static or instance field of class. In the OpenJDK implementation invocations of such handles result in a corresponding call to an method on
sun.misc.Unsafe, after appropriate safety checks have been performed. For example, if the field is a reference type (a non-primitive type) marked as volatile then the method
Unsafe.putObjectVolatile will be invoked.
If such a reference to a
MethodHandle is held in a static final field then the runtime should be able to constant fold invocations on that reference and what it holds when inlining occurs. In such cases, perhaps surprisingly, the generated machine code can be competitive with direct invocation of methods on
get/putfield byte codes instructions.
Note: It is straightforward to extend the
MethodHandle implementation to support handles for relaxed, lazy and compare-and-set atomic operations by invoking the appropriate method on
MethodHandle giving write access to a non-static field, "vfield" say of type
Value, on a class,
Receiver say, can be obtained as follows:
An exact invocation of that
MethodHandle will then set the value of the field "vfield" on an instance of
Note that the receiver instance is passed as the first parameter to the
invokeExact method. The receiver provides the base location from which to access the value of field, "vfield", it holds (since there is no direct l-value and pass by reference of fields, or array elements, supported in Java a pair of receiver and value is necessary).
MethodHandle.invokeExact is declared as a polymorphic signature method:
When javac compiles invocations to signature polymorphic methods it uses a symbolic type descriptor as the method signature, which is derived from actual parameter and return types of the caller and not the method signature of the method declaration.
An example of an invokevirtual instruction is shown as follows:
Notice that the method signature accepts two arguments, a instance of a class
Receiver and class
Value, and returns void, this signature is referred to as the symbolic type descriptor.
An inlining trace of such an invocation, when the handle is constant folded, is as follows:
The invocation is comprised of two stages. The first stage performs an efficient run-time safety check to determine if the symbolic type descriptor encoded at the call site exactly matches the method type descriptor of the
MethodHandle. The second stage performs the write access, in this case to a volatile field.
MethodHandler.invokeExact invocation is intrinsically linked (see section "Linking of
invokeExact invocations") to the static method
invokeExact_MT, on a dynamically generated class, the byte code of which is:
The parameters for
invokeExact_MT are as follows:
- the parameters
(r, v)passed to the
invokeExactmethod; and finally
- the call site's symbolic type descriptor, appended when the call site is linked.
Notice that at this point the reference parameter types are erased to
Object, thus the class declaring this static method can be shared for invocations with different method type descriptors that erase to the same signature.
This method first performs the method type descriptor check and if that fails an exception is thrown, otherwise it is safe to proceed as it is known the parameter types and return type of the call site are correct and exactly match. Next, the
invokeBasic on the
MethodHandle instance is invoked with the same parameters passed to the
The invocation of
invokeBasic is intrinsically linked to the static method
putObjectVolatileFieldCast on a dynamically generated class corresponding to the compiled lambda form of the
vmentry field of the
LambdaForm of the
MethodHandle is the
MemberName that characterizes the method
putObjectVolatileFieldCast, the byte code of which is:
The first parameter is the
MethodHandle instance and the subsequent parameters are those,
(r, v), passed to the
invokeExact method. The
MethodHandle instance is a direct handle that holds the field offset to be used with the invocation of
Unsafe.putObjectVolatile at the end of this method. Before that invocation:
- a safety check is performed to ensure the receiver instance is not
- a cast check of the value instance to an instance of the value (field) type is performed to ensure the runtime compiler has sufficient information to perform type profiling. Note that this is not required for type safety since such a safety check was already performed by the
invokeExact_MTmethod; observe that the type of the receiver instance does not require a cast to an instance of the receiver type.
Linking of invokeExact invocations
MethodHandler.invokeExact are intrinsically linked via an up call from the VM to a Java method that returns a
MemberName characterizing the Java method to be linked to. This up-called Java method, statically known to the VM, is
The "type" parameter is either an instance of
String corresponding to the symbolic type descriptor.
The “appendixResult” is used to return an optional extra parameter that must match the last parameter of the method characterized by the
MemberName, and will be permanently appended at the linked call site.
On invocation of
invokeExact the VM stack already contains three values and the VM will add one additional parameter onto the call stack such that the parameters are as follows:
- the parameters
(r, v); and finally the additional parameter that is
- the first element of the "appendixResult", which is the call site's symbolic type descriptor.
Thanks to John Rose for providing useful comments and feedback.