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 | the pypy angle is to shrug and copy the implementation of CPython as closely as possible, and staying out of design decisions
jcea1 has joined #pypy
jcea has quit [Read error: Connection reset by peer]
jcea1 is now known as jcea
jcea has quit [Ping timeout: 246 seconds]
jcea has joined #pypy
Guest60 has joined #pypy
<Guest60> Regarding my qs from last week: thanks to @cfbolz' kind suggestions, I was able to get very promising results from my rpython bytecode interpreter. The two biggest wins were (a) rewriting interpreter data structures as full classes, and (b) shimmering between machine ints and bigints. I am very impressed with how the JIT has been able to produce
<Guest60> roughly the same performance even when I gratuitously added a closure call (using its captured environment) to the innermost loop of the interpreted code.
Guest60 has quit [Quit: Client closed]
<cfbolz> Guest60: there's a ton of potential left, I think
jinsun has quit [Ping timeout: 246 seconds]
Guest60 has joined #pypy
<Guest60> excellent ... then I'll dig into the JIT visualiser next (but I have checked with a separate rpython project and the factorial is now within 90% of the necessary uninterpreted bigint muls)
<Guest60> is there anything I can set to get the visualiser to open in full-screen mode by default?
Guest60 has quit [Quit: Client closed]