cfbolz changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end ) | use cffi for calling C | if a pep adds a mere 25-30 [C-API] functions or so, it's a drop in the ocean (cough) - Armin
todda7 has quit [Ping timeout: 246 seconds]
oberstet has quit [Read error: Connection reset by peer]
glyph has quit [Quit: End of line.]
glyph has joined #pypy
Techcable has quit [Quit: Techcable - The Lounge]
jcea has quit [Ping timeout: 240 seconds]
Techcable has joined #pypy
lritter has quit [Ping timeout: 265 seconds]
lritter has joined #pypy
Techcable has quit [Quit: ZNC - https://znc.in]
Techcable has joined #pypy
Techcable is now known as Guest68433
Guest68433 has quit [Quit: ZNC - https://znc.in]
Techcable_ has joined #pypy
_whitelogger has joined #pypy
Techcable has quit [Quit: ZNC - https://znc.in]
Techcable has joined #pypy
Techcable is now known as Guest47497
Guest47497 has quit [Quit: ZNC - https://znc.in]
Techcable_ has joined #pypy
forgottenone has joined #pypy
forgottenone has quit [Remote host closed the connection]
forgottenone has joined #pypy
pmp-p has quit [Ping timeout: 265 seconds]
pmp-p has joined #pypy
lritter has quit [Ping timeout: 265 seconds]
todda7 has joined #pypy
jcea has joined #pypy
forgottenone has quit [Read error: Connection reset by peer]
muke has joined #pypy
<muke> Hey cfbolz, been looking at the make_execute_token some more, does the implementation in llmodel actually already work out the box as long as I provide a working looptoken? It seemed as if some parts weren't implemented so I wasn't sure
<cfbolz> muke: I think so
<muke> right that's good then, one thing I'm wondering though is how to provide get the values frame_info needs from LLVM - it wants the size in bytes as well as the depth of the frame?
<muke> what is the depth here
<muke> is it just the stack depth itself?
<cfbolz> I think it's something like the maximum values spilled into the frame, in a "normal" backend
<muke> ah
<cfbolz> so for you it's something like "the maximum size of the failargs", maybe? I suspect you can progress by just using some fixed size for a bit
<cfbolz> "8"
<muke> I was thinking something like that yea
ronan has joined #pypy
forgottenone has joined #pypy
oberstet has joined #pypy
Dejan has joined #pypy
Dejan has joined #pypy
Dejan has quit [Changing host]
Dejan_ has joined #pypy
Dejan has quit [Ping timeout: 265 seconds]
Dejan_ has quit [Client Quit]
Dejan has joined #pypy
Dejan has quit [Changing host]
Dejan has joined #pypy
oberstet has quit [Remote host closed the connection]
oberstet has joined #pypy
Techcable_ is now known as Techcable
Gustavo6046 has quit [Remote host closed the connection]
Gustavo6046 has joined #pypy
<mattip> wow the lib-python/3/test/test_warnings/__init__.py tests are convoluted
<cfbolz> mattip: thanks for looking into it
<cfbolz> I think I gave up once already
<mattip> it seems they mock everything, so I am not sure what exactly the test is meant to do
<exarkun> Boo mocks
todda7 has quit [Ping timeout: 264 seconds]
oberstet has quit [Quit: Leaving]
jacob22 has joined #pypy
RemoteFox has joined #pypy
RemoteFox has left #pypy [#pypy]
lritter has joined #pypy
muke has quit [Remote host closed the connection]
dddddd has quit [Ping timeout: 256 seconds]
dddddd has joined #pypy
raekye is now known as david236
david236 is now known as raekye
forgottenone has quit [Ping timeout: 260 seconds]