cfbolz changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://botbot.me/freenode/pypy/ ) | use cffi for calling C | "the modern world where network packets and compiler optimizations are effectively hostile"
<kenaan>
mattip cpyext-leakchecking c1d2c7124ad5 /rpython/rtyper/: fix translation by adding immortal to malloc in rpython (grafted from e3219c61e7a801f5257cba1a9df98aa1...
<kenaan>
rlamy cpyext-leakchecking d7afdd455feb /pypy/interpreter/baseobjspace.py: Add option to prevent caching in space.appexec() (for cpyext tests)
<kenaan>
rlamy cpyext-leakchecking d893df676f94 /pypy/module/cpyext/test/test_dictobject.py: Move 2 tests from app- to interp-level to fix refcounting issues
<kenaan>
cfbolz arrays-force-less da044fcdd451 /: a branch to try to not force the whole array after a lazy setarrayitem is forced, but only the affected ...
<kenaan>
cfbolz arrays-force-less 7a124bb988d9 /rpython/jit/metainterp/optimizeopt/: a small improvement to getarrayitem caching when invalidating getarrayitem caches due to a setarrayitem...
* arigato
writes examples in the cffi tests where CPython's cyclic GC suffers from the same problem as PyPy's GC: unexpectedly large objects, causing the GC to think everything's fine when it's not
<arigato>
it seems that __pypy__.add_memory_pressure() should really exist on CPython, too
mihneas has joined #pypy
mihneas has quit [Client Quit]
<LarstiQ>
how would it work with cpython's gc?
<LarstiQ>
__pypy__ calling gc.collect?
<arigato>
unsure
<cfbolz>
arigato: argh
bgola_ is now known as bgola
lritter has joined #pypy
<fijal>
arigato: that sounds like a major bikeshedding topic :)
* fijal
is stuck trying to deal with banks
nimaje1 has joined #pypy
nimaje1 is now known as nimaje
nimaje has quit [Killed (verne.freenode.net (Nickname regained by services))]
<kenaan>
arigo cffi/cffi 120347b84c08 /: Add an optional 'size' argument to ffi.gc(). So far, it has no effect on CPython.
marky1991 has quit [Ping timeout: 260 seconds]
<kenaan>
antocuni default 620fefe235f3 /lib-python/2.7/distutils/unixccompiler.py: Add a workaround to make the distutils options 'runtime_library_dirs' working. Fixes #2593
adamholmberg has joined #pypy
<kenaan>
arigo default 53cb371f1828 /pypy/module/_cffi_backend/: Call add_memory_pressure(size) in response to ffi.gc(..., size)
<fijal>
arigato: you sure it did not get (somehow) fixed on py3k?
<arigato>
fijal: I checked in CPython 3.7
<make>
Hey! :) I'm trying to build PyPy from the source. My question would be, would running make in the directory and following these instructions do the same thing? http://doc.pypy.org/en/latest/build.html
<make>
I did the former, but I am not sure if I made the pypy-c executable.
<LarstiQ>
make: running make is fine
<make>
Is there anything else I need to do after running make then? I still get an error when trying to use PyPy
<arigato>
fijal: talking about the GC in CPython? yes, this changed
<arigato>
it has nothing to do with the problem I described here, though
<arigato>
or at least their solution has nothing to do, because that solution is still based on the number of objects, not the size that each object keeps around
<fijal>
ah
<make>
I tried to package the version I ran make on but I keep getting this error: Please compile pypy first, using translate.py, or check that you gave the correct path with --override_pypy_c
lritter has quit [Quit: Leaving]
<LarstiQ>
make: doing what? It sounds like you just typed 'pypy' which won't do anything
<LarstiQ>
you need to run the pypy-c binary it produced
<make>
LarstiQ: how do I run it?
<arigato>
I think this error means that "make" didn't succeed
<arigato>
otherwise, there is a "pypy/goal/pypy-c" binary
<arigato>
ah, or maybe a "./pypy-c" binary, not inside "pypy/goal"
<arigato>
and, re "ah", it might be because of this different location that you get the error
<kenaan>
cfbolz arrays-force-less 82b3076c7887 /: close to-be-merged branch
<arigato>
anyone has any objection if I change the Makefile inside pypy to produce "pypy/goal/pypy-c", as done by all other documented ways and as expected by all other places?
<cfbolz>
arigato: yes please
<arigato>
we neither test, not really document, the Makefile
<kenaan>
cfbolz default a22d0969f40a /: merge arrays-force-less don't throw away all of the knowledge about an array when forcing a lazy setarrayitem. in...
<make>
arigato: This might sound like a stupid question, but after packaging, how do I install and run? I have tried everything, but it seems like I'm not doing the correct thing.
<arigato>
unpack the .tar.bz2 file somewhere, and run "bin/pypy" there
<arigato>
we recommend /opt/pypy5.8/ as a place, for example
<mattip>
so we do not properly handle user-defined classes ?
* mattip
off to a movie
mattip has left #pypy ["bye"]
jcea has quit [Quit: jcea]
<antocuni>
ronan: I think that revdb works by using an rpython transformation which logs all the read/writes to known objects. If it's raw memory, it cannot possibly keep track of it
<ronan>
antocuni: yes, but here all the writes are done from Python code, so I'm hoping there's a way to simulate watching it
<antocuni>
no clue, sorry :(
mattip has joined #pypy
<kenaan>
mattip cpyext-leakchecking c1786ec814d9 /pypy/module/cpyext/typeobject.py: maybe identify a possible leak in handling GetSetProperty?
<mattip>
ronan: that commit has nothing to do with user-defined classes, but GetSet has also been troubling me
jacob22_ has quit [Quit: Konversation terminated!]
<mattip>
now I am really away
mattip has left #pypy ["bye"]
<ronan>
mattip (logs): AFAICT, it's never released
<kenaan>
cfbolz getarrayitem-into-bridges f105d8c2eae7 /rpython/jit/metainterp/: support for caching infos on constants, while I'm at it
lritter has joined #pypy
lritter has quit [Remote host closed the connection]
lritter has joined #pypy
antocuni has quit [Ping timeout: 240 seconds]
yuyichao_ has joined #pypy
yuyichao has quit [Ping timeout: 255 seconds]
yuyichao_ has quit [Ping timeout: 246 seconds]
kanaka has quit [Remote host closed the connection]
yuyichao_ has joined #pypy
slackyy has quit [Ping timeout: 240 seconds]
lritter has quit [Quit: Leaving]
mvantellingen has joined #pypy
tbodt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]