On 8 April 2015 at 04:54, Yuriy Taraday <yorik.sar(a)gmail.com> wrote:
> Did you miss mailing list intentionally?
>
Ach no! I always seem to do this on pypy-dev. Thanks for pointing that
out.
>
> On Tue, Apr 7, 2015 at 5:59 PM William ML Leslie <
> william.leslie.ttg(a)gmail.com> wrote:
>
>> On 8 April 2015 at 00:00, Yuriy Taraday <yorik.sar(a)gmail.com> wrote:
>>
>>> GC introduces concurrency to user code anyway: call to some …
[View More]__del__
>>> method can happen in any time in user code, so it might be called in a
>>> separate thread just as well
>>>
>>
>> Obligatory: http://wingolog.org/archives/201
>>
>> 2/02/16/unexpected-concurrency
>>
>
> Yes, that's how I see it: one can't bet on where and when finalizers are
> run, so they appear to the rest of the program as if they're run in some
> special thread that wake ups in some scary moments. So a separate thread is
> just as good for them.
>
Except that, up until now, you can expect that __del__ is run in /one/ of
the threads you've started. If you only have one thread, you know exactly
which thread your __del__ will be run in. So you could make assumptions
about thread-local state when you write such a method.
Not that I have an opinion here. __del__ is problematic, and entirely to
be avoided in new code, afaiac.
--
William Leslie
Notice:
Likely much of this email is, by the nature of copyright, covered under
copyright law. You absolutely MAY reproduce any part of it in accordance
with the copyright law of the nation you are reading this in. Any attempt
to DENY YOU THOSE RIGHTS would be illegal without prior contractual
agreement.
[View Less]
Hi Team,
I am building out the pypy 2.5.0 from source on linux. I built this using
oel 6.3 which has a gcc 4.4.7 and built fine, however with oel 5.6 with a
gcc version 4.1.2, it fails on the creation of libpypy-c.so shared library
with the following error:
/usr/bin/ld: implement.o: relocation R_X86_64_PC32 against
`pypy_asm_stackwalk' can not be used when making a shared object; recompile
with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: ld returned 1 exit status
I rechecked …
[View More]that gcc asserts fPIC for position independent code, however it
still fails and I don't have this problem on 4.4.7 gcc. Could I know the
recommended gcc version for building pypy 2.5.0.
I am sorry the recommended approach is to use an older version of pypy to
build the newer version however we have a unique situation in our build
environment where pypy is built using 2.7.5 python. I know this may not be
relevant in this context but thought I should say so.
Thanks in Advance,
-Roshan
[View Less]
Hi all,
The allegro64 buildslave seems to have definitely disappeared last
week, with no warning to most of us. It used to run the nightly
64-bit Linux translations and tests. Do we have another Linux machine
available?
Armin
Hey pypy-devs,
Thanks a lot for you amazing work for pypy!
I have a naive question regarding pypy's performance, I was doing some
performance testing with pypy, at first i was using a sample size of 9000,
our script was able to process this batch in 2.8 sec, which gives us a rate
of 3200/s, which we thought was somewhat slow. Then we changed to a sample
size of 1 million, the speed was as slow initially but soon ramped up and
stabilized at around 40k/s which is more than enough for us.
I am …
[View More]just curious what cause the performance ramp up, thanks a lot!
Cheng
[View Less]
