[pypy-dev] how do you parse jit log containing binary dump ?

[Shubha Ramani]

Yury:
I am no longer confused about that. But so far, in order to be able to dump jitcodes, I have to instrument python code with"JitDriver", "merge_point", "meta_interp", etc...under the test directory - and  the resulting toy python program I write in order to get the jit dump HAS TO BE rpython compliant. For instance, I tried to write a toy program which calls "divmod" under the test directory -can't do that, since it's disallowed by rpython.
I was responding to Richard's earlier statement:"Jitlog is data generated by the JIT compiler. Without a jitdriver, it
will not be able to JIT compile any code, thus you cannot obtain that
file. If you do not have a rpython program, you cannot really generate
the jitlog easily."
 

    On Friday, December 9, 2016 6:50 AM, Yury V. Zaytsev <yury at shurup.com> wrote:
 

 On Fri, 9 Dec 2016, Shubha Ramani via pypy-dev wrote:

> I'm building a tool which attempts to map Jit ByteCodes back to the 
> actual function which was called at the Python level. Therefore I need 
> to map the Jit ByteCodes back to the actual function address - the 
> physical address not the virtual. It seems like to build this tool I 
> have to get the rpython version of the open source benchmark - which is 
> not an easy task. I would like to take any old Python application out in 
> the wild and instrument it to dump jitcodes using rpython as an 
> interpreter. Is this possible ?

It seems to me that you are confused about the relationship between 
RPython and PyPy. The former is the translation toolchain, and the latter 
is the implementation of Python on the basis of this toolchain.

-- 
Sincerely yours,
Yury V. Zaytsev


   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20161209/cd9541d2/attachment-0001.html>