The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around a hundred and forty sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo

← Accept All Archive

PyTorch BlogTools

From KTIR to SpyreCode: An MLIR Dataflow Backend for IBM Spyre

10.20

TL;DR Torch-spyre’s Inductor decides how each kernel’s work is divided across Spyre’s cores and manages tensor residency between on-chip scratchpad and off-chip memory, and the backend compiler turns…

Chips & compute

Read at PyTorch Blog ↗

One letter a week, starting soon.

Latest

From KTIR to SpyreCode: An MLIR Dataflow Backend for IBM Spyre

Related

VoicesPhysical AI at NVIDIA Software Engineering Daily

LabsHugging Face ❤️ TorchTPU: TPUs, Natively Hugging Face Blog

ToolsIntroducing vLLM TorchTPU vLLM Blog

SiliconNvidia Vera’s System Architecture: Pushing Bandwidth Chips and Cheese

SiliconAccelerating Mamba-2 with High-Performance Forward Pass Kernels in NVIDIA CUDA Tile NVIDIA Technical Blog

ToolsNVIDIA Vera CPUs double throughput for Modal Sandboxes Modal