On May 9, 2012, at 8:30 PM, Charles Oliver Nutter wrote:
> Thanks for the update, John! Comments below...
>
> On Wed, May 9, 2012 at 2:34 PM, John Rose wrote:
>> In JDK 7 FCS a method handle is represented as a chain of argument
>> transformation blocks, ending in a pointer to a methodOop. The
On May 10, 2012, at 12:16 AM, Jeroen Frijters wrote:
> Thanks for the update. This sounds great. It looks like this would be helpful
> for me as well. Is the LambdaForm stuff written in Java?
Yes, all in Java. This refactoring moves a lot of stuff up-stack from assembly
to C++ and C++ to Java.
vm-dev-
> boun...@openjdk.java.net] On Behalf Of John Rose
> Sent: Wednesday, May 09, 2012 21:35
> To: Da Vinci Machine Project
> Subject: Lazy Method Handle update
>
> Lazy Method Handles is a project to defer code generation for method
> handle behavior, and minimize require
Thanks for the update, John! Comments below...
On Wed, May 9, 2012 at 2:34 PM, John Rose wrote:
> In JDK 7 FCS a method handle is represented as a chain of argument
> transformation blocks, ending in a pointer to a methodOop. The argument
> transformations are assembly coded and work in the in
from John
There may be a type-safe way to use them...
Well since I only have one type I guess I don't have to wait -)
regards
mark___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
On May 9, 2012, at 1:37 PM, Mark Roos wrote:
>
> Quite interesting John. A few curiosity based questions.
>
> we are now representing the argument transformations using
> a simple AST-like IR, called a LambdaForm
>
> would this be something we could inspect, build or manipu
Quite interesting John. A few curiosity based questions.
we are now representing the argument transformations using
a simple AST-like IR, called a LambdaForm
would this be something we could inspect, build or manipulate?
This form can be easily rendered down to bytecod
Lazy Method Handles is a project to defer code generation for method handle
behavior, and minimize requirements for support from hand-written assembly code.
The idea is to make all method handle behavior visible to the JVM compiler, so
that it can be optimized properly. Assembly code cannot be
