[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pypy-dev
Subject:    Re: [pypy-dev] Faster PyPy translation (for debugging)
From:       wlavrijsen () lbl ! gov
Date:       2012-05-24 14:24:52
Message-ID: alpine.LNX.2.00.1205240715580.14238 () pc3-wlav ! lbl ! gov
[Download RAW message or body]

Hi Timothy,

> On my machine that takes about 800sec before it starts rtyping my
> module. Are there some better options I can use if I simply want to
> make sure that my module will fit into the PyPy typesystem?

if it can find the errors, then the fastest is to use:

    pypy/bin/checkmodule.py <yourmodule>

but I very rarely find errors that way. Second is to write a jit test,
which does partial translation (only of the code reachable from the test)
and can use a fake space, which really speeds things up. Look at any of the
jit tests themselves or those in module (*/test/*jit*.py) for some examples.
It's a bit of work (and I didn't write mine, but got it from one of the
core pypy folks :) ), but I find it in practice by far the quickest way to
find rtyping errors (albeit, again, not always conclusive).

HTH,
   Wim
-- 
WLavrijsen@lbl.gov    --    +1 (510) 486 6411    --    www.lavrijsen.net
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
[prev in list] [next in list] [prev in thread] [next in thread]