[pypy-dev] gsoc for pypy...

Benoit Boissinot bboissin+pypy at gmail.com
Tue Mar 2 20:40:49 CET 2010

On Tue, Mar 2, 2010 at 8:35 PM, Armin Rigo <arigo at tunes.org> wrote:
> 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.

On the other hand, it looks like the US guys made it production
quality, isn't it?
(At least it seems they generate correct code)


More information about the Pypy-dev mailing list