On Fri, Feb 17, 2012 at 3:29 PM, Antonio Cuni <[email protected]> wrote: > On 02/17/2012 02:27 PM, Timothy Baldridge wrote: >>> >>> In pypy we have a custom opcode to call methods, which is much faster >>> than >>> LOAD_ATTR/CALL_FUNCTION. See e.g. how this piece of code gets compiled: >>> >> >> Excellent! I was unaware of this. Just last night I started >> abstracting some bytecode generation to support both 2.6 and 2.7, so >> it won't be hard to slot in improvements for pypy. >> >> From there, I'll start looking into jitviewer. > > > I suggest to look at the jitviewer before doing this. I might be wrong and > LOAD_ATTR/CALL_FUNCTION be efficient enough, I don't know. > > Also note that you should hit reply-all when replying, else you send the > email only to the author and not to the ML (I re-added pypy-dev in CC). > > > ciao, > Anto > _______________________________________________ > pypy-dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/pypy-dev
Hi Timothy. First question - why did you choose to implement this as a compiler to python bytecode? It does sound like an interpreter written in rpython would have both a much better performance and a much easier implementation (compiler vs interpreter). Cheers, fijal _______________________________________________ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
