Re: [pypy-dev] pypy1.6 slow on string-heavy ops

2011-08-19 Thread Armin Rigo
Hi Jacob, On Fri, Aug 19, 2011 at 2:10 AM, Jacob Biesinger jake.biesin...@gmail.com wrote: A bit OT:  The recent release of ipython added some powerful multiprocessing features using ZeroMQ.  I've only glanced at pypy's extensive threading optimizations (e.g., greenlets).  Does pypy jit across

Re: [pypy-dev] PPC64 JIT test_ppc.py tests fixed and working

2011-08-19 Thread Sven Hager
On 08/18/2011 09:51 PM, David Edelsohn wrote: Sven, With the attached patch, all of the ppc/ppcgen/test/test_ppc.py tests pass except for test_call_function that I skip while I debug it. I updated ppc_assembler.py:load_from() to load a full 64 bit value on 64 bit systems. It is not exactly

Re: [pypy-dev] work on libpypy.so

2011-08-19 Thread Roberto De Ioris
Il giorno 25/lug/2011, alle ore 14:31, Armin Rigo ha scritto: Indeed, there is nothing like that so far. We need to think out the kind of C-level API which makes sense for libpypy.so to expose. There are two options: either we tweak a little bit cpyext to expose the CPython C API, or we

[pypy-dev] Build pypy 1.6 on Windows XP with MinGW: can't find ffi.h

2011-08-19 Thread Caleb Hattingh
Hi This is a really silly thing, but I am hoping someone who has done this before can just give me the one-liner answer. I am trying to build pypy 1.6 on Windows XP using MinGW (in an MSYS environment). The build gets started, and I see a bit of Mandelbrot, but when the time comes for JIT, I

Re: [pypy-dev] Saving and reloading JIT optimizations

2011-08-19 Thread Armin Rigo
Hi David, On Fri, Aug 19, 2011 at 1:56 PM, David Fraser dav...@sjsoft.com wrote: The pypy JIT takes a while to work out which parts of python code need optimization etc, and only after that phase do the speedups become relevant. Have there been any efforts (indeed, is it a feasible idea at

Re: [pypy-dev] Saving and reloading JIT optimizations

2011-08-19 Thread Massa, Harald Armin
The pypy JIT takes a while to work out which parts of python code need optimization etc, No, this is not really doable.  The JIT writes explicitly in the assembler the address of a ton of constants. could a special logging area be of use? as in JIT decides foo_do_something_often() is

Re: [pypy-dev] Build pypy 1.6 on Windows XP with MinGW: can't find ffi.h

2011-08-19 Thread Caleb Hattingh
On 19 August 2011 18:55, Caleb Hattingh caleb.hatti...@gmail.com wrote: I ran out of memory some time after the JIT had successfully compiled, so now I am trying PYPY_GC_MAX_DELTA=200MB pypy --jit loop_longevity=300 ./translate.py -Ojit as suggested in the help page.  Will post here again if