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
forgottenone has quit [Quit: Konversation terminated!]
<arigo>
rindolf: as far as I can tell, the two programs are very different: the Python one has to handle very large integers in recursive_a_sequence(), the C++ one blindly truncates to 32 bits
<arigo>
...right, the C++ one truncates to 128 bits actually
<rindolf>
arigo: yes
<arigo>
but the Python one handles it as large integers (more than 63 bits)
<arigo>
we have no special logic to detect "ah but the integers always fit in 127 bits so let's use __int128"
<arigo>
this makes an important difference, specially for operations like "%"
Rhy0lite has quit [Ping timeout: 240 seconds]
<arigo>
that's one thing I can think about. the remaining difference is probably the expected fact that a C compiler generates better machine code than our JIT
<arigo>
and also the extra overhead of managing "seq" as a generator
speeder39_ has joined #pypy
Rhy0lite has joined #pypy
marvin has quit [Remote host closed the connection]
marvin has joined #pypy
marvin has quit [Remote host closed the connection]
marvin has joined #pypy
todda7 has quit [Remote host closed the connection]
todda7 has joined #pypy
todda7 has quit [Read error: Connection reset by peer]
todda7 has joined #pypy
speeder39_ has quit [Quit: Connection closed for inactivity]