@avi it's just trees,
Let's chat about compilers
@avi it's just trees,
I feel like if I'm not careful I might get into XSLT
Heating water from afar: https://bernsteinbear.com/blog/heating-water-from-afar/?utm_source=rss
In which I connect some wires
Preprint by Christoph Jung and me is now online: 'Low Overhead Allocation Sampling in a Garbage Collected Virtual Machine'
https://arxiv.org/abs/2506.16883
Just presented weval at PLDI -- talk is at https://www.youtube.com/watch?v=ubfPyMCvhXs#2h26m in the livestream (2:26:00 or thereabouts if timestamp doesn't work). Tons of great discussions about this and many other things -- wish I could spend more time at conferences! (I suppose I wouldn't have any time to do the work to present here, then.) Thanks to coauthor @tekknolagi for the help getting this published.
What I talk about when I talk about IRs
@lynn this (& linear scan) has been bothering me for some months now
@pervognsen happy to give a walkthrough/pair on it after PLDI!
Just saw the coolest demo Boris Shingarov, Jan Vraný on the MPLR stream: a instruction-stepping debugger of a RISC-V core, but it was integrated with the Sail specification so you could step *into* the RISC-V instruction to see what the specification says the instruction should do.
@Yhg1s I am curious what the other responses look like. I have no idea what a normal python user is
I think probably the 38M wasm blob with a small wasm interpreter is better. ICFP2006 rise up
Wow! brotli got it down to 7.8M!! But at what cost?
gzips nicely to 18M. Still waiting on brotli to finish.
So there's gojekyll. And Go can compile to wasm+wasi. And w2c2 can compile that to C. So here I am wondering if I should bundle the 212M gojekyll.c with my blog,
@sbrunthaler @mattpd @cfbolz a) it's the Facebook MO; see all the other ones but b) it's not from scratch. It's a patchset
@mattpd @cfbolz @sbrunthaler the internal project is still going but quietly (for now)