Patrick Wright a écrit : > John > > Thanks for the update. > > >> 5. encourage the great work that people are doing or will do on tail >> call, continuations, interface injection, invokedynamic, etc. >> (Cheers, Arnold, Lukas, Tobias, Remi.) >> > > It would be great to get an update on how these sub-projects are > going, what they are (currently, realistically) aiming to achieve, > etc. Perhaps the people involved can give us a brief status update? > Rémi = invokedynamic backport be able to use method handle and invokedynamic on 1.5 VM current status: in limbo :) more precisely, the project work by detecting invokedynamic call or method handle calls and translate them to an equivalent sequence of bytecodes. I use ASM to find and patch. So currently there is a special branch of ASM named invokedynamic that is able to read and write invokedynamic calls using the lastest invokedynamic format (the one without receiver, i.e the one of the upcoming spec).
MethodHandle supports was almost ready before John changes the format of MethodType (to add varargs bits). I haven't updated the corresponding ASM templates yet. Invokedynamic supports need to be totally re-designed because it is based on the assertion that the method bootstrap on an invokedynamic call is available during the loading of the bytecode. This assertion seems to be false. That's the risk of life on bleeding edge :) I will able to fully update the backport during my next vacation, in the end of february. > > Thanks! > Patrick > Regards, Rémi _______________________________________________ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
