The curious case of MHS.Lookup.unreflect on MethodHandle.invoke/invokeExact
John Rose
john.r.rose at oracle.com
Fri Mar 20 05:45:42 UTC 2015
On Mar 18, 2015, at 3:59 AM, Paul Sandoz <paul.sandoz at oracle.com> wrote:
>
> Perhaps such method handles were originally cached to avoid an explosion (deliberate or otherwise) of class generation of LFs, but now there is more sophisticated LF caching in place this is not necessary.?
That's probably correct. Per-MT caching is overkill for all but the most crucial MHs. — John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/mlvm-dev/attachments/20150319/ea65f773/attachment.html>
More information about the mlvm-dev
mailing list