On Aug 12, 2011, at 9:49 PM, Charles Oliver Nutter wrote:
> On the other side of things...I hope those languages that will churn
> through method handles also realize they're unlikely to ever JIT...
Getting native code out of the MH-construction process brings them much closer
to optimizability.
Twenty-year-old systems with "method handles" (i.e., lambdas) are very good at
compiling them.
If you have a curried function (one which requires something like MH.bindTo on
every call) you can optimize it after inlining the full call sequence and then
using escape analysis to scalarize the intermediate MHs.
That's what we have to do, if we are going to support Lambdas which are invoked
in the curried style. (I can't see how we wouldn't support them.) Happily,
JVMs already do EA, so our job is primarily a matter of making MHs scrutable to
that algorithm.
-- John
_______________________________________________
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
