cfbolz changed the topic of #pypy to: #pypy PyPy, the flexible snake | IRC logs: and | Matti: I made a bit of progress, the tests now only segfault towards the end
<glyph> so I wanted to go give PyPy a try on Apple Silicon since it's been a while since landed
<glyph> but I cannot find a nightly build to download
<glyph> the only two macosx_arm64's on are 0 bytes
<glyph> I am falling pretty deep into this rabbit hole, I downloaded a pypy2 that seems to be functional and now I'm translating pypy3 myself, I don't really know why I am doing this given that I have no idea if the relevant changes are even on the py3.9 branch
<glyph> I see some mandelbrots though so cool I guess
<LarstiQ> :)
<LarstiQ> glyph: from reading what fijal and mattip write here, my impression is that it's still a little early for the Apple silicion pypy
<glyph> LarstiQ: Yeah, I mean, I'm expecting to report bugs
<glyph> LarstiQ: I am not gonna look at mandelbrot ascii art getting generated on my own terminal and then think to myself "I bet this is pretty robust production software, let me put it into production"
<glyph> LarstiQ: any pointers for me to not just waste a bunch of time translating something that's gonna fail with a traceback after 2 hours?
<glyph> like what branch to check out, etc
<LarstiQ> I don't remember seeing that mentioned on irc, I'd have to dig for a relevant looking commit
<glyph> LarstiQ: also, just curious, is any of this stuff cached? or is every translation the same multi-hour exercise
<glyph> okay now we're to the compilation stage and dang this is the first thing that has caused this machine's fans to turn on that didn't involve 3D rendering
<glyph> and they are _very_ on
<glyph> ↪ Thu Jun 16 23:39:10 PDT 2022 (★ PATH="${PATH}:/Users/glyph/Downloads/pypy-c-jit-105731-00a230410d68-macosx_arm64/bin" pypy ../../rpython/bin/rpython --make-jobs=12 --opt=jit) (1286 seconds elapsed)
<glyph> it runs pip
<glyph> well, this was definitely a surprise]
<glyph> I feel like 21 minutes is a pretty good translation time?
<glyph> runs twisted too, dang, this like, 100% works great, good job everybody
<LarstiQ> glyph: no caching on translations, that idea keeps resurfacing throughout the years but is an actual research project
<LarstiQ> and yes, translation time is pretty good on that fancy hardware :)
<glyph> LarstiQ: I'd much rather get parallelism than caching, not that my opinion means anything here :)
<glyph> 2 minute translation times could really improve development though I'd imagine
<LarstiQ> perhaps, but pypy devs are used to not translating all the time and developing with tests
<LarstiQ> I myself am mostly a lurker though
<glyph> woohoo and it's 2x as fast as cpython on this hardware
<glyph> at least in this one extremely stupid microbenchmark
<LarstiQ> :)
<LarstiQ> (my understanding of the translation is that it's a whole-program analysis, making the caching and parallelism a bit trickier)
<glyph> yeah I certainly understand what it's a difficult problem
<glyph> frankly if arigo can't figure it out I have no hope of even approaching the problem
<LarstiQ> glyph: if you have a bachelor/master/phd student for cfbolz I'm sure he'd be happy to supervise such work ;)
* cfbolz waves
<cfbolz> glyph: yeah, it's our oldest piece of technical debt
Dejan has joined #pypy
Atque has quit [Remote host closed the connection]
Atque has joined #pypy
Atque has quit [Remote host closed the connection]
Atque has joined #pypy
<mattip> glyph: thanks for the heads up, I didn't notice the macos package upload was empty.
<mattip> should be fixed now
<mattip> fwiw, there is still something fishy with vararg and libffi, see for instance this issue
Atque has quit [Write error: Connection reset by peer]
Atque has joined #pypy
mattip has left #pypy [Leaving]
derpydoo has joined #pypy
Guest96 has joined #pypy
Guest96 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
derpydoo has quit [Ping timeout: 255 seconds]