cfbolz changed the topic of #pypy to: #pypy PyPy, the flexible snake https://pypy.org | IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end and https://libera.irclog.whitequark.org/pypy | Matti: I made a bit of progress, the tests now only segfault towards the end
Atque has quit [Ping timeout: 268 seconds]
Atque has joined #pypy
tsraoien has joined #pypy
tsraoien has quit [Ping timeout: 244 seconds]
Atque has quit [Remote host closed the connection]
Atque has joined #pypy
jcea has quit [Ping timeout: 264 seconds]
Atque has quit [Remote host closed the connection]
Atque has joined #pypy
Atque has quit [Remote host closed the connection]
Atque has joined #pypy
Atque has quit [Quit: ...]
<mattip> any comments/thoughts on the M1 blog post?
<mattip> fijal: ^^^
<fijal> let me have a look
<fijal> I mean, it's very minimal :)
<fijal> maybe it's worth noting that arm64 support has been around for a while (sponsored by RPi foundation?), but there are a few interesting OS X specifics that needed adressing
<fijal> (but I'm also ok if not)
<mattip> thanks, I will add that
j4at has joined #pypy
j4at has quit [Remote host closed the connection]
<cfbolz> fijal: the arm64 support was sponsored by crossbar and arm ltd, I think
j4at has joined #pypy
j4at has quit [Ping timeout: 268 seconds]
Dejan has quit [Quit: Leaving]
<mattip> I added a mention, without the sponsor. How does it look now?
<fijal> ok
<fijal> mattip: seems to work, more or less?
MiguelX413 has joined #pypy
<mattip> fijal: what seems to work, the blog post or to the M1 port?
<mattip> if you are OK with the post I will publish it soon
<mattip> agreed it is more of an extended tweet than a real blog post, but there doesn't seem to be more to say
<fijal> yes I'm ok with the post
<fijal> arm64 seems to more or less work
<fijal> mattip: I agree
<mattip> ok, publishing
<cfbolz> awesome
<cfbolz> will tweet
commandoline has quit [Quit: Bye!]
commandoline has joined #pypy
j4at has joined #pypy
<j4at> mattip: the opencollective url is incorrect
<cfbolz> Ah, an extra ')'
<cfbolz> j4at: thanks a lot, I pushed a fix
<j4at> ;)
<j4at> cgbolz: does pypy have logic to disable inlining locally or does it only disable it globally ?
<j4at> cfbolz *
jcea has joined #pypy
jcea has quit [Client Quit]
jcea has joined #pypy
<cfbolz> j4at: so by default there is some heuristic for inlining decisions
<cfbolz> I'm not sure what the hooks expose
<j4at> the hooks doesn't expose anything other than stoping inlining globally
<j4at> Can't do anything with that
<j4at> I will do retracing seeems easier with what is exposed rn. I learned how to read the operations kinda I will try to use that. Needs per loop/bridge `get_stats_snapshot()` tho.
<j4at> Without retracing If I use `max()` builtin function with a list in warmup. max with tuples becomes 2x slower.
<j4at> there is a huge performance lose there
j4at has quit [Read error: Connection reset by peer]
Dejan has joined #pypy
Dejan has quit [Quit: Leaving]
jcea has quit [Ping timeout: 264 seconds]
shimst3r has quit [Ping timeout: 260 seconds]
shimst3r has joined #pypy
Dejan has joined #pypy
shimst3r has quit [Ping timeout: 268 seconds]
shimst3r has joined #pypy
<krono> Nice blogpost, everyone. Kudos for the work!
kor1_ has joined #pypy
kor1_ is now known as kor1
kor1 has left #pypy [https://quassel-irc.org - Chat comfortably. Anywhere.]
Atque has joined #pypy
Atque has quit [Quit: ...]
<antocuni> I'm reading a lot about WebAssembly nowadays, and I stumbled upon this page: https://github.com/WebAssembly/design/blob/main/Tooling.md
<antocuni> it's nice to see that pypy is explicitly mentioned as one of the examples of JITs
jcea has joined #pypy