Hi All,
anybody knows how to check if a method is jitted or not?
I remember (maybe wrongly) that the Jit in Cog has a configurable limit on
the number of bytecodes for a method to be jitted or not; I'm looking into
the performance of generated code where I can, more or less, control the
length of
2015-02-23 14:05 GMT+01:00 Thierry Goubier :
> Hi All,
>
Hello,
>
> anybody knows how to check if a method is jitted or not?
>
I don't think there's a way to do that.
>
> I remember (maybe wrongly) that the Jit in Cog has a configurable limit on
> the number of bytecodes for a method to be jit
Hi Clement,
2015-02-23 14:46 GMT+01:00 Clément Bera :
>
> Any method is jitted if when activated it's already in the global lookup
> cache and it's not already jitted (so mostly on second calls).
>
Ok.
>
> The only limit is on the number of literals. A method with more than a
> certain number
2015-02-23 15:08 GMT+01:00 Thierry Goubier :
> Hi Clement,
>
> 2015-02-23 14:46 GMT+01:00 Clément Bera :
>
>>
>> Any method is jitted if when activated it's already in the global lookup
>> cache and it's not already jitted (so mostly on second calls).
>>
>
> Ok.
>
>
>>
>> The only limit is on the
Hi Thierry,
there's an unadvertised primitive called Context>>#xRay (or
ContextPart>>#xRay) that answers these questions for tests. I'm away from the
system right now but I'll get you the source soon. Also, the limit on jutting
methods, 60 literals, is a default. There's a command line o
2015-02-23 16:36 GMT+01:00 Eliot Miranda :
> Hi Thierry,
>
> there's an unadvertised primitive called Context>>#xRay (or
> ContextPart>>#xRay) that answers these questions for tests. I'm away from
> the system right now but I'll get you the source soon. Also, the limit on
> jutting methods,
