Re: Loopy CallSite

2014-07-16 Thread Christian Thalinger
On Jul 16, 2014, at 11:40 AM, Remi Forax wrote: > > On 07/16/2014 07:38 PM, Vladimir Ivanov wrote: >> Remi, >> >> The problem is that for every iteration you create new call site >> > for(int i=0; i<100_000; i++) { >> >new LoopyCS().getTarget().invokeExact(1_000); >> > } >>

Re: Loopy CallSite

2014-07-16 Thread Remi Forax
On 07/16/2014 07:38 PM, Vladimir Ivanov wrote: Remi, The problem is that for every iteration you create new call site > for(int i=0; i<100_000; i++) { >new LoopyCS().getTarget().invokeExact(1_000); > } In LoopyCS constructor you instantiates 3 new MethodHandles: >targ

Re: Loopy CallSite

2014-07-16 Thread Vladimir Ivanov
Remi, The problem is that for every iteration you create new call site > for(int i=0; i<100_000; i++) { >new LoopyCS().getTarget().invokeExact(1_000); > } In LoopyCS constructor you instantiates 3 new MethodHandles: >target = MethodHandles.filterArguments(target, 0, FOO

Re: Loopy CallSite

2014-07-12 Thread Remi Forax
On 07/12/2014 08:08 PM, Charles Oliver Nutter wrote: I played with this some years ago. Doesn't it just become recursive, because it won't inline through the dynamicInvoker? - Charlie (mobile) It's clearly recursive. I don't think it's a good idea to try to fully inline it anyway, it will

Re: Loopy CallSite

2014-07-12 Thread Charles Oliver Nutter
I played with this some years ago. Doesn't it just become recursive, because it won't inline through the dynamicInvoker? - Charlie (mobile) On Jul 12, 2014 9:36 AM, "Remi Forax" wrote: > It seems that the JIT is lost with whe there is a loopy callsite and never > stabilize (or the steady state i