Re: another question about megamorphic call sites in combination with MethodHandles

2013-03-22 Thread Remi Forax
On 03/22/2013 11:12 AM, Jochen Theodorou wrote: > Am 22.03.2013 10:35, schrieb Remi Forax: >> On 03/22/2013 10:24 AM, Jochen Theodorou wrote: >>> Am 22.03.2013 10:11, schrieb Remi Forax: >>> [...] I don't think it's a good idea to expose directly method handles to users, it's better to en

Re: another question about megamorphic call sites in combination with MethodHandles

2013-03-22 Thread Jochen Theodorou
Am 22.03.2013 10:35, schrieb Remi Forax: > On 03/22/2013 10:24 AM, Jochen Theodorou wrote: >> Am 22.03.2013 10:11, schrieb Remi Forax: >> [...] >>> I don't think it's a good idea to expose directly method handles to users, >>> it's better to encapsulate it into a Groovy object corresponding to a >>

Re: another question about megamorphic call sites in combination with MethodHandles

2013-03-22 Thread Remi Forax
On 03/22/2013 10:24 AM, Jochen Theodorou wrote: > Am 22.03.2013 10:11, schrieb Remi Forax: > [...] >> I don't think it's a good idea to expose directly method handles to users, >> it's better to encapsulate it into a Groovy object corresponding to a >> function or a closure so you can add a bunch o

Re: another question about megamorphic call sites in combination with MethodHandles

2013-03-22 Thread Jochen Theodorou
Am 22.03.2013 10:11, schrieb Remi Forax: [...] > I don't think it's a good idea to expose directly method handles to users, > it's better to encapsulate it into a Groovy object corresponding to a > function or a closure so you can add a bunch of invoke overloads. what invoke overloads are you thin

Re: another question about megamorphic call sites in combination with MethodHandles

2013-03-22 Thread Remi Forax
On 03/22/2013 10:06 AM, Remi Forax wrote: > On 03/22/2013 07:52 AM, Jochen Theodorou wrote: >> Am 21.03.2013 20:49, schrieb Remi Forax: >> [...] >>> I suppose you take a look to the instances. >>> You can do something similar actually by using invokedynamic + >>> a guardWithTest that checks already

Re: another question about megamorphic call sites in combination with MethodHandles

2013-03-22 Thread Remi Forax
On 03/22/2013 07:57 AM, Jochen Theodorou wrote: > Am 21.03.2013 20:31, schrieb Krystal Mo: >> Hi Jochen, >> >> At least with the current tip version of HotSpot, the >> mh.invokeWithArguments() callsite is not likely to get its actual target >> inlined into the caller; we depended a lot on being abl

Re: another question about megamorphic call sites in combination with MethodHandles

2013-03-22 Thread Remi Forax
On 03/22/2013 07:52 AM, Jochen Theodorou wrote: > Am 21.03.2013 20:49, schrieb Remi Forax: > [...] >> I suppose you take a look to the instances. >> You can do something similar actually by using invokedynamic + >> a guardWithTest that checks already seen instances instead of doing a >> plain mh.in