Hi Ruochen,
On 5 May 2016 at 08:17, 黄若尘 <[email protected]> wrote:
> Recently I’m trying to apply a new tracing JIT policy to Pyrlang, I found
> there are some traces that were too long and therefore aborted by JIT
> according to rpython’s JIT log.
You can find them without using JitHookInterface:
jitdriver = JitDriver(..., get_printable_location=get_printable_location)
Then get_printable_location() should translate the greenkey into a
human-readable string that describes the location. Once this is done,
you can usually figure out why some specific traces are too long by
looking at the PYPYLOG output:
PYPYLOG=jit:log pyrlang-c args...
This produces a file called "log" where the output of
`get_printable_location()` is found in the `debug_merge_point`
intructions, so that you should be able to follow it (even it is a bit
large).
A bientôt,
Armin.
_______________________________________________
pypy-dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-dev
