Compiling with -O0 is really quick, but the runtime is fairly slow. I haven't tried with -O1. -O2 takes a few seconds to compile, but that plus runtime is still faster than the pypy version with jit, but not by too much (I'm recalling the tests I did with the mandelbrot program specifically). I can get some actual numbers later today.<div>
<br></div><div>Sure I'll write up a post. This was a lot of fun, and I think it's a great way to teach people how pypy works.</div><div><br></div><div>-Andrew<br><br><div class="gmail_quote">On Thu, Mar 31, 2011 at 8:33 AM, Antonio Cuni <span dir="ltr"><<a href="mailto:anto.cuni@gmail.com">anto.cuni@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On 31/03/11 14:28, Andrew Brown wrote:<br>
> In any case, I'm satisfied with the speed. It's still beaten by a BF to C<br>
> translator combined with gcc -O2 though, that'd be a tough case to beat. =)<br>
<br>
</div>what happens if you combine the BF to C with gcc -O0 or -O1?<br>
<br>
Anyway, I think that if you feel like writing a post explaining your<br>
experience with using pypy and its jit for writing an interpreter, we could<br>
publish it on our blog. I suppose it would be useful/interesting for other<br>
people as well.<br>
<br>
What do the others think?<br>
</blockquote></div><br></div>