invocation. Then they are compiled to
bytecode and then JIT kicks in. That's why you see continuous JITing.
If you reuse a call site object, it stabilizes very quickly.
Best regards,
Vladimir Ivanov
On 7/12/14 6:05 PM, Remi Forax wrote:
It seems that the JIT is lost with whe there is a loopy
On 7/12/14 6:05 PM, Remi Forax wrote:
It seems that the JIT is lost with whe there is a loopy callsite and
never stabilize (or the steady state is after the program ends).
import java.lang.invoke.MethodHandle;
import java.lang.invoke.MethodHandles;
import java.lang.invoke.MethodType;
import
quickly.
doh, sorry for this stupid code :(
Everyone makes mistakes once in a while. Even you, Remi ;-)
Best regards,
Vladimir Ivanov
Rémi
On 7/12/14 6:05 PM, Remi Forax wrote:
It seems that the JIT is lost with whe there is a loopy callsite and
never stabilize (or the steady state
It seems that the JIT is lost with whe there is a loopy callsite and
never stabilize (or the steady state is after the program ends).
import java.lang.invoke.MethodHandle;
import java.lang.invoke.MethodHandles;
import java.lang.invoke.MethodType;
import java.lang.invoke.MutableCallSite;
public
, it will
generate too much assembly code.
The actual problem is that the JIT generate assembly code and then try
again, and again, and again ...
Rémi
On Jul 12, 2014 9:36 AM, Remi Forax fo...@univ-mlv.fr
mailto:fo...@univ-mlv.fr wrote:
It seems that the JIT is lost with whe there is a loopy
