On Sun, Jul 5, 2009 at 1:17 PM, Rémi Forax<[email protected]> wrote: > Else, for slow paths, you can use a JavaMethodHandle and store > all you need using fields instead of insert them as arguments. > It's very difficult to write a JavaMethodHandle that doesnt not box/spread > to handle polymorphic signatures that why I think it should > only be used to handle slow paths.
The down side of constructing a JavaMethodHandle is that if the additional arguments to the test are different we'd end up constructing new every time. Obviously avoiding arg boxing is key to performance, so call paths will need to support a large number of unboxed arguments to allow passing call protocols along cleanly. I'll play around with things a bit and see if there's anything specific to the call site that could be generated once, avoiding the extra arguments... - Charlie _______________________________________________ mlvm-dev mailing list [email protected] http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
