marvin has quit [Remote host closed the connection]
marvin_ has joined #pypy
Guest60 has joined #pypy
Guest60 has quit [Client Quit]
jinsun has joined #pypy
[Arfrever] has quit [Ping timeout: 246 seconds]
[Arfrever] has joined #pypy
jcea has joined #pypy
sthalik has quit [Remote host closed the connection]
jcea has quit [Ping timeout: 240 seconds]
Guest60 has joined #pypy
<Guest60>
no problem, it turns out that one can either make the window bigger or the blocks smaller (by reducing how many jit ops get kept), and making the blocks fit in the small window was wonderful incentive for me to cajole the JIT into doing the latter ;)
<Guest60>
the bridges generated for `gcd` are more complex than I would do by hand (although I don't think it affects wall-clock time much, just space, and that's cheap these days), but the loops generated for `cfac` and `csum` look optimal (just 5-6 jit ops for 15 interpreted bytecodes) and match timings for handwritten straight rpython.
Guest60 has quit [Quit: Client closed]
jinsun has quit [Ping timeout: 246 seconds]
jinsun has joined #pypy
jcea has joined #pypy
jinsun_ has joined #pypy
jinsun_ is now known as jinsun
jinsun is now known as Guest4653
Guest4653 has quit [Ping timeout: 246 seconds]
jinsun_ has joined #pypy
jinsun_ is now known as jinsun
jinsun is now known as Guest9598
Guest9598 has quit [Ping timeout: 246 seconds]
<hexology>
is there a recommended version of pypy to use for bootstrapping a clean build, for a package distro that wants to rebuild things from source?
<nimaje>
well, then probably cpython2.7 and I think the only diffrence should be how long the build takes, but you wouldn't need pypy binaries
hexology- has joined #pypy
hexology has quit [*.net *.split]
<hexology->
nimaje: got it. it's a very big difference in build time and memory usage though, right?