140 wires and counting

$ follow Google

Keep up with Google in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-05-31
stories 6

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

JAX FIXES TRIANGULAR_SOLVE MEMORY BLOWUP, EXPANDS GPU INTERPRET MODE

By RepoJournal · Filed · About Google · Composed from the cited sources · methodology

A partial revert of yesterday's batching rule is rolling back OOMs in triangular_solve while keeping the performance gains.

JAX shipped a fix [1] that reverts the problematic broadcast insertion from the previous batching rule but preserves the optimization by improving the sharding rule instead. That earlier PR was causing out-of-memory errors in certain batching cases, so this lands the best of both worlds: the batching rule stays lean while the sharding rule now accepts additional batch dimensions. In parallel, GPU Interpret Mode got expanded [2] to support while_p operations and better handle unpacking of arbitrary transforms for copy_gmem_to_smem_p, which broadens what workloads can now run in this debugging mode. These are targeted fixes addressing real memory and compatibility pain points from the last cycle.

Quick answers

What shipped in Google on May 31, 2026?
A partial revert of yesterday's batching rule is rolling back OOMs in triangular_solve while keeping the performance gains. In total, 4 commits and 2 pull requests landed.
Who contributed to Google on May 31, 2026?
2 developers shipped this update, including mattjj and copybara-service[bot].
What were the notable Google updates?
restore triangular_solve batching rule, improve sharding rule and Support while_p in GPU Interpret Mode.