cfbolz changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://botbot.me/freenode/pypy/ ) | use cffi for calling C | mac OS and Fedora are not Windows
speeder39_ has joined #pypy
marky1991 has quit [Read error: Connection reset by peer]
<kenaan>
antocuni gc-disable 2db479ad4b70 /: improve the return value of gc.collect_step: now it returns a GcCollectStepStats, the same which is passed to...
<cfbolz>
arigato: note that the trace that gets produced is a bit funny. Do I see it correctly that it starts with the while, and then goes via the break through the for loop back to the while again?
<arigato>
cfbolz: I didn't get to know that, I was expecting a backend issue and debugging assembly
<cfbolz>
arigato: ah
<cfbolz>
arigato: your debug print shows that it's a frontend problem though, right?
<arigato>
yes, I gave up when I realized that and posted my current debug_print solution to the issue
<cfbolz>
Right
<cfbolz>
Fun times ahead :-(
<arigato>
and indeed, copying the debug_print at the end of the loop shows that 'height' is equally broken there, which makes sense if the end of the loop is always just before the start of the next iteration
<cfbolz>
That height changes at all is just weird
<arigato>
yes
<cfbolz>
Maybe it's some kind of weird state matching problem
<arigato>
as a clue, I think there is somewhere close a short preamble taken
<arigato>
unrelated, but I'm sending a mail to everbody on pypy-dev---but with a different subject for everybody. Maybe that will let us track who forwards his mails to the westhost issue tracker
<cfbolz>
arigato: ah, you are sending these mails spread out across time to see who it is?
<arigato>
no, just with a different subject. They are also spread out across time but that's only because I can't easily send 833 mails at once
<cfbolz>
Ah, subject, makes sense
<arigato>
the issue tracker's reply contains the same subject as the original mail
<cfbolz>
Cool
[Arfrever] has joined #pypy
<arigato>
found it
tsutsumi has quit [Quit: Ping timeout (120 seconds)]
marky1991 has quit [Read error: Connection reset by peer]
<arigato>
piem: you were asking about cffi, some not completely clear question
<arigato>
if by "reading the code generated by cffi" you mean the C code generated by cffi, then yes, it only contains CPython-specific argument parsing if compiled with CPython
<arigato>
we PyPy we choose the simpler solution of not providing it, and instead relying on libffi to do the calls when not JITted, and on our JIT when JITted
<arigato>
we could have done the same with CPython, but the cost would never be removed, so it's more noticeable
<arigato>
regarding your timings, it's hard to conclude anything because they are all close to each other
<arigato>
and well, we can't guess what exactly is the code doing
adamholmberg has quit [Remote host closed the connection]