This version seems to have inconsistent removal of ignore profile in the
hotspot patch. It’s no longer added to vmSymbols but is still referenced
in classFileParser.
On 19/01/2015 20:21, "MacGregor, Duncan (GE Energy Management)"
wrote:
>Okay, I¹ve done some tests of this with the micro benchmar
Duncan, sorry for that.
Updated webrev inplace.
Best regards,
Vladimir Ivanov
On 1/21/15 1:39 PM, MacGregor, Duncan (GE Energy Management) wrote:
> This version seems to have inconsistent removal of ignore profile in the
> hotspot patch. It’s no longer added to vmSymbols but is still referenced
>
Btw,
I have a few 50% discounts left for the VM tech day. If you are interested,
please e-mail me directly!
/Marcus
> On 19 Jan 2015, at 10:58, Marcus Lagergren
> wrote:
>
> And to further clarify things - you can attend _only_ the VM Tech day / tech
> summit, should you so desire, and skip
http://cr.openjdk.java.net/~vlivanov/8069591/webrev.00/
https://bugs.openjdk.java.net/browse/JDK-8069591
Overhead of non-inlined MH.invoke/invokeExact calls significantly
increased with LambdaForm sharing. The cause is JIT compiler can't
produce a single nmethod for the whole MethodHandle chain
Hi Vladimir,
in Invokers.java, I think that checkCustomized should take an Object and
not a MethodHandle
exactly like getCallSiteTarget takes an Object and not a CallSite.
in MethodHandle.java, customizationCount is declared as a byte and there
is no check that
the CUSTOMIZE_THRESHOLD is not
On Jan 21, 2015, at 9:31 AM, Remi Forax wrote:
>
> in Invokers.java, I think that checkCustomized should take an Object and not
> a MethodHandle
> exactly like getCallSiteTarget takes an Object and not a CallSite.
The use of erased types (any ref => Object) in the MH runtime is an artifact of
