[Vm-dev] Re: [Pharo-dev] Determine if a method is Jitted or not
eliot.miranda at gmail.com
Mon Feb 23 15:36:12 UTC 2015
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 option -maxcoglits (IIRC) that you can change.
On Feb 23, 2015, at 5:05 AM, Thierry Goubier <thierry.goubier at gmail.com> wrote:
> 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 methods (SmaCC) and I'd like to find the optimum point.
More information about the Vm-dev