RepoJournal
PyTorch

@pytorch

PyTorch and the broader machine-learning ecosystem

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

One email a day. Unsubscribe in one click.

Pick a date

Topics: Python AI / ML Full archive →

The Wire · Showcase

EXECUTORCH ADDS TURBOQUANT TO GEMMA4, PYTORCH PURGES FLAKY DYNAMO TESTS

By RepoJournal · Filed · About PyTorch

1 person shipped this

ExecutorchGemma 4 31B can now handle arbitrarily long contexts with TurboQuant 4-bit KV cache compression, while PyTorch is ripping out the dynamo_eager and aot_eager integration tests that have been bleeding flakiness into trunk.

The ExecutorTorch team shipped TurboQuant TQ4 support for the MLX backend [1], compressing full-attention KV caches from bf16 to 4-bit codebooks plus per-vector norms. This lets Gemma 4 31B-IT scale to very long contexts without touching sliding-window layers. The same team landed fuse() implementations across all remaining Cadence QuantizationPattern subclasses [2] [3] and enabled QuantFusionPass in the compiler pipeline [4], unifying quantization fusion logic across backends. On the PyTorch side, the compiler team is nuking the dynamo_eager and aot_eager integration tests from inductor-periodic CI [5], which have been chronic sources of flakiness without generating useful signals. Concurrently, they're decoupling the aoti_cross_compile_for_windows shard from the main cuda13 test job [7], so Windows build breaks no longer take down an entire day of CUDA testing. The inductor team also fixed a C++ Most Vexing Parse bug in cpp_wrapper_cpu_array_ref [6] that was breaking thread_local declarations when constructors were involved. Dynamo tooling is getting hardened too: debug and repro utilities are being made device-agnostic [8] so non-CUDA accelerators can actually generate reproduction scripts.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] [MLX][Gemma4] Add turbo quant support (#19866) pytorch/executorch
  2. [2] Add fuse() to remaining QuantizationPatterns (#19727) ↗ pytorch/executorch
  3. [3] Add fuse() to QuantizationPatterns (#19726) ↗ pytorch/executorch
  4. [4] Enable QuantFusionPass in compiler pipeline (#19728) (#19728) pytorch/executorch
  5. [5] [CI] Nuke all the dynamo_eager and aot_eager integration tests (#185224) pytorch/pytorch
  6. [6] [inductor] Fix C++ Most Vexing Parse in cpp_wrapper_cpu_array_ref (#185257) (#185257) pytorch/pytorch
  7. [7] Decouple aoti cross-compile shard from main cuda13 test job (#185680) pytorch/pytorch
  8. [8] Make dynamo debug/repro utilities device-agnostic (#184851) pytorch/benchmark

Quick answers

What shipped in PyTorch on May 30, 2026?
ExecutorchGemma 4 31B can now handle arbitrarily long contexts with TurboQuant 4-bit KV cache compression, while PyTorch is ripping out the dynamo_eager and aot_eager integration tests that have been bleeding flakiness into trunk. In total, 79 commits, 25 pull requests, and 2 releases landed.
Who contributed to PyTorch on May 30, 2026?
1 developer shipped this update, including ethansfng.
What were the notable PyTorch updates?
[MLX][Gemma4] Add turbo quant support (#19866), Add fuse() to remaining QuantizationPatterns (#19727), and Add fuse() to QuantizationPatterns (#19726).

More from @pytorch

Daily updates, in your inbox

Follow PyTorch

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

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?