The current JIT generator creates a tracing jit, which gives very different performance profile to static compilation. For tight loops etc this might be ok, but might be different for the specific use case people are interested in (I admit I still don't know what that is).
On 26/09/2010 1:47 AM, "horace grant" <[email protected]> wrote: i just had a (probably) silly idea. :) if some people like rpython so much, how about writing a rpython interpreter in rpython? wouldn't it be much easier for the jit to optimize rpython code? couldn't jitted rpython code theoretically be as fast as a program that got compiled to c from rpython? hm... but i wonder if this would make sense at all. maybe if you ran rpython code with pypy-c-jit, it already could be jitted as well as with a special rpython interpreter? ...if there were a special rpython interpreter, would the current jit generator have to be changed to take advantage of the more simple language? just curious... On Tue, Sep 7, 2010 at 11:07 AM, Stefan Behnel <[email protected]> wrote: > Armin Rigo, 07.09.20...
_______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
