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

[Maciej Fijalkowski]

On Thu, May 24, 2012 at 6:19 PM, Timothy Baldridge <tbaldridge at gmail.com>wrote:

> > 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?
>
>
> Side note, I would really love to see the JVM backend more maintained.
> If I could write Clojure in RPython, then run it on the JVM...with a
> full tracing JIT, that would just be insanely awesome.
>
> Timothy
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> http://mail.python.org/mailman/listinfo/pypy-dev
>

Note that you don't get the full tracing JIT for free with JVM. As in the
RPython implementation at the first approximation would just directly
translate to JVM bytecode and be happy (and slow). To add a tracing JIT for
the JVM you need some significant work, see antonio cuni's thesis for his
work on .NET

Cheers,
fijal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20120524/4019b1ed/attachment.html>