[pypy-dev] CTypes backend for Cython Status

2011-09-07 Thread Romain Guillebert
Hi The Google Summer of Code has ended and I didn't give the current status to anyone yet (I was very busy with a report I had to write for my university). There is still work to do on the project (there was more work than I expected, especially because of semantic differences between Cython and

Re: [pypy-dev] segfault in translation; C backend

2011-09-07 Thread wlavrijsen
Hi, [reply-ing to myself] one of those things: I spent a several days banging my head on this and then explaining it in an e-mail is enough to focus my thoughts and solve it. That said, I'm not 100% sure what's going on. What I know is that I have an opaque (or so I thought!) handle type, namel

[pypy-dev] segfault in translation; C backend

2011-09-07 Thread wlavrijsen
Hi, I have a crash in the translation chain when I enable the CINT back-end, and I just don't seem to be able to figure it out: [c] 132000 nodes [ array: 15760 framework rtti: 724 func: 10234 group: 1 struct: 131169 ] * [c] 133000 nodes [ array: 16008 framework rtti: 738 func: 10312

Re: [pypy-dev] deepcopy slower in PyPY ?!

2011-09-07 Thread Maciej Fijalkowski
On Wed, Sep 7, 2011 at 8:16 PM, Antonio Cuni wrote: > Hi Jorge, > > On 07/09/11 16:43, Jorge de Jesus wrote: >> >>  Hi to all >> >> I've benchmark/profile  some code (PyWPS API) and PyPy-c is 2/3x times >> slower than CPython.  This was done in a virtual machine using x86_64 >> >> The code being b

Re: [pypy-dev] deepcopy slower in PyPY ?!

2011-09-07 Thread Antonio Cuni
Hi Jorge, On 07/09/11 16:43, Jorge de Jesus wrote: Hi to all I've benchmark/profile some code (PyWPS API) and PyPy-c is 2/3x times slower than CPython. This was done in a virtual machine using x86_64 The code being benchmark spends most of the time making calls to copy/deepcopy. I've foun

[pypy-dev] deepcopy slower in PyPY ?!

2011-09-07 Thread Jorge de Jesus
Hi to all I've benchmark/profile some code (PyWPS API) and PyPy-c is 2/3x times slower than CPython. This was done in a virtual machine using x86_64 The code being benchmark spends most of the time making calls to copy/deepcopy. I've found that this was an issue in PyPy 1.6 (https://bugs.pypy