Re-hi, On Tue, Mar 02, 2010 at 08:22:51PM +0100, Armin Rigo wrote: > Yes, but I bet from experience that we're going to run after a few days' > work into the next issue. We've already done that 3 or 4 times with > llvm, so now I'm honestly a bit fed up. For comparison, gcc gives code > that is a bit slower but at least it is really a solid bug-free project.
Let me make this statement more precise: I mean for the non-JIT backends of PyPy, using the llvm backend of PyPy gaves results that were typically a little bit faster than using the C backend, when compiling with llvm-gcc. However, with the various generations of our JIT, using a JIT llvm backend always ran into llvm bugs. A bientot, Armin. _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
