mattpd

@TomF@mastodon.gamedev.place On that note, also like John Ousterhout's "Always measure one level deeper", https://al.radbox.org/doi/10.1145/3213770

"If you want to understand the performance of a system at a particular level, you must measure not just that level but also the next level deeper. That is, measure the underlying factors that contribute to the performance at the higher level."

@adrian@discuss.systems That works, thanks!

@adrian@discuss.systems Ah, not just me, then! I'm blaming them wild ASPLOS folks taking ideas like the Asemantic Code Revolution too far! Thanks for the service in any case, this is a vast improvement over the ACM DL "experience" :-)

@adrian@discuss.systems Thanks! BTW, am I the only one getting "Abstract: Data missing." with https://al.radbox.org/doi/10.1145/3779212.3790241 It does show up on https://dl.acm.org/doi/10.1145/3779212.3790241 FWIW

@glennklockwood BTW, these findings look interesting: https://specdecode-bench.github.io/

@glennklockwood See also Speculative Speculative Decoding, https://arxiv.org/abs/2603.03251 https://github.com/tanishqkumar/ssd

When AI Writes the World’s Software, Who Verifies It?

https://leodemoura.github.io/blog/2026/02/28/when-ai-writes-the-worlds-software.html

"Writing a specification forces clear thinking about what a system must do, what invariants it must maintain, what can go wrong. This is where the real engineering work has always lived. Implementation just used to be louder."

@neilhenning@mastodon.gamedev.place @nikic@mastodon.social Somewhat related (a different ecosystem, albeit MLIR-based) but this looks like an interesting idea: Triton Extensions: a framework for developing and building Triton compiler extensions https://github.com/triton-lang/triton-ext/ Presented a few days ago: https://www.youtube.com/watch?v=JnFFwBB6Dhk&t=781s Allows to develop custom passes, dialects, backends, and language extensions downstream without having to fork the upstream compiler codebase.