Hi,
I am currently investigating here some performance issues and I may have
found a culprint here - invokeExact. My case is one where method caching
fails and I will have to do an invokeExact from Java - meaning without
the invokedynamic bytecode and with a non constant method handle. I am
Which version of the jvm are you seeing this problem on, and are you
adapting the method handle every time as well as exact invoking it?
We avoided invoke and invokeExact calls from Java (because they were
sometimes painful to get correct in the case of varargs methods) by having
the fallbacks
On May 7, 2013, at 8:04 AM, Jochen Theodorou blackd...@gmx.org wrote:
Hi,
I am currently investigating here some performance issues and I may have
found a culprint here - invokeExact. My case is one where method caching
fails and I will have to do an invokeExact from Java - meaning
On 05/07/2013 07:31 PM, Christian Thalinger wrote:
On May 7, 2013, at 8:04 AM, Jochen Theodorou blackd...@gmx.org wrote:
Hi,
I am currently investigating here some performance issues and I may have
found a culprint here - invokeExact. My case is one where method caching
fails and I will
On May 7, 2013, at 3:44 PM, Remi Forax fo...@univ-mlv.fr wrote:
I understand why you need a trampoline for a virtual call but
why do you need a trampoline for a static call ?
The arguments have to be reordered, since the MH is a leading argument that
must be deleted (in the case of a DMH).
