Re: [pypy-dev] Work on the JVM backend
2012/1/12 Michał Bendowski : > Hello everyone, > > Back in the summer I asked on this mailing list if there's interest in moving > the JVM backend forward. Back then there was some enthusiasm, so I got back > to it when I had the chance, which unfortunately was a few months later. The > suggestion back then was to look into using JPype to integrate more closely > with Java-side code, and that's what I would like to do. Hi Michal, I'm afraid I'm only a pypy observer, so I can't help with your specific queries. However, I want to say that I'm cheering for your effort to get the JVM backend up and running again! I tried to look at it a little a few months ago, but couldn't quite get it to translate for me (not sure why, but I ran out of time to play with it). Someday I'd like to see Jython integrate with PyPy somehow, but I'm fuzzy on the how :) Anyway though I don't know what was suggested with respect to JPype I'd like suggest a look at another Java integration point. JDK 7 was recently released and it contains invokedynamic, which would be likely to be a great help with some sorts of Java integration. Here are some relevant links: http://jcp.org/en/jsr/detail?id=292 http://docs.oracle.com/javase/7/docs/api/java/lang/invoke/package-summary.html http://openjdk.java.net/projects/mlvm/ https://wikis.oracle.com/display/mlvm/Home Again, I don't know the details about how JPype would be used exactly, I just wanted to make sure you knew about invokedynamic. -Frank Wierzbicki ___ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] Work on the JVM backend
On Thu, Jan 12, 2012 at 3:06 PM, Alex Gaynor wrote: > I'm mostly an observerer on the JVM + PyPy front, but my understanding is > JPype or the like would be to solve the issue of "how do we test this > without compiling all of PyPy". Ah I see - a very different point of integration. Thanks for the clarification! -Frank ___ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
[pypy-dev] Translating just the parser for JVM [was: Faster PyPy translation (for debugging)]
On Thu, May 24, 2012 at 7:24 AM, wrote: > if it can find the errors, then the fastest is to use: > > pypy/bin/checkmodule.py > > 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 ___ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] Translating just the parser for JVM [was: Faster PyPy translation (for debugging)]
On Thu, May 24, 2012 at 9:19 AM, Timothy Baldridge wrote: > 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. Holy turtles all the way down batman! :) -Frank ___ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] Translating just the parser for JVM [was: Faster PyPy translation (for debugging)]
On Thu, May 24, 2012 at 9:31 AM, Michal Bendowski wrote: > Just two add my two cents: I made the JVM backend translate the > standard interpreter in the jvm-improvements branch a few months ago > (just a few changes). The branch has been closed though and I had a > busy time so I didn't do anything about it. > > For the last few weeks/months I was sitting in my cave and working on > my thesis, which now lets you use JVM classes directly in RPython > (rjvm) and also contains a naive, reflection-based jvm module for the > resulting interpreter. I know this is not in the OSS spirit, but it so > happened, sorry. I'm planning to merge my changes soon and hopefully > keep on working on the JVM backend. Nice! Can't wait to see it - and of course I understand that working on a thesis makes people disappear :) -Frank ___ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
