Re: [pypy-dev] GC error

2012-01-16 Thread Timo Paulssen
Hello, PyPy has a hard limit on its heap size. It can be specified with this environment variable: PYPY_GC_MAXThe max heap size. If coming near this limit, it will first collect more often, then raise an RPython MemoryError, and if

Re: [pypy-dev] GC error

2012-01-16 Thread Rich Drewes
On 01/16/2012 02:02 PM, Romain Guillebert wrote: Hi PyPy may use more memory than cpython because of the JIT, can you try without the JIT (by passing --jit off to the interpreter) ? When I run with --jit off it gives a MemoryError at about the same point in the run, but with no exception trac

Re: [pypy-dev] GC error

2012-01-16 Thread Romain Guillebert
Hi PyPy may use more memory than cpython because of the JIT, can you try without the JIT (by passing --jit off to the interpreter) ? Cheers Romain On Mon, Jan 16, 2012 at 7:44 PM, Rich Drewes wrote: > Hello all, > > Great work on pypy!  I've had good luck with pypy generally but on a program >

Re: [pypy-dev] Work on the JVM backend

2012-01-16 Thread Michał Bendowski
On Monday, 16 January 2012 at 13:53 , Antonio Cuni wrote: > On 01/16/2012 01:03 PM, Michał Bendowski wrote: > > > I have copied the hash(self) from ootype._instance – didn't consider > > subclasses messing with __hash__. Anyway, as compute_identity_hash is > > defined as the RPython equivale

[pypy-dev] GC error

2012-01-16 Thread Rich Drewes
Hello all, Great work on pypy! I've had good luck with pypy generally but on a program that loads a very large data set I am getting a GC related exception: loading reads, on record 2500 RPython traceback: File "translator_goal_targetpypystandalone.c", line 888, in entry_point F

Re: [pypy-dev] Work on the JVM backend

2012-01-16 Thread Antonio Cuni
On 01/16/2012 01:03 PM, Michał Bendowski wrote: I have copied the hash(self) from ootype._instance – didn't consider subclasses messing with __hash__. Anyway, as compute_identity_hash is defined as the RPython equivalent of object.__hash__(x), the "stub implementation" in _builtin_type (and _i

Re: [pypy-dev] Work on the JVM backend

2012-01-16 Thread Michał Bendowski
On Monday, 16 January 2012 at 12:09 , Antonio Cuni wrote: > Hello Michał, > > On 01/16/2012 01:00 AM, Michał Bendowski wrote: > > longlong2float and float2longlong turn out to be pretty straightforward in > > Java, so I implemented them and added tests. I tried to update the pull > > request

Re: [pypy-dev] Work on the JVM backend

2012-01-16 Thread Antonio Cuni
Hello Michał, On 01/16/2012 01:00 AM, Michał Bendowski wrote: longlong2float and float2longlong turn out to be pretty straightforward in Java, so I implemented them and added tests. I tried to update the pull request to include this commit, but that crashed BitBucket :/ Maybe you can just pull

Re: [pypy-dev] Some NumPyPy propositions

2012-01-16 Thread Dmitrey
Hi, On 01/14/2012 08:22 PM, Maciej Fijalkowski wrote: Hi Dmitrey. Let me answer your questions one by one. On Thu, Jan 12, 2012 at 11:42 AM, Dmitrey wrote: hi all, I would like to make some propositions wrt NumPy port development: 1) It would be nice to have a build and/or install parameter