[pypy-dev] Translating just the parser for JVM [was: Faster PyPy translation (for debugging)]

[fwierzbicki at gmail.com]

On Thu, May 24, 2012 at 7:24 AM,  <wlavrijsen at lbl.gov> wrote:

> 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).
I've been meaning to dip a toe in PyPy but had trouble getting the JVM
translator to work the last time I tried. How hard would it be to use
a fake space (or some other technique) to just spit out a parser for
the JVM?

-Frank