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

HALIDE FUSION BUG CRUSH, ROCM DEADLOCK FIXES ACROSS THE STACK

By RepoJournal · Filed · About PyTorch

PyTorch's Halide backend had a critical inplace mutation fusion bug that could silently corrupt results on aliased reads, and it's not alone: ROCm deadlocks are being systematically hunted across FBGEMM and core compute kernels.

The Halide inplace mutation fusion fix [1] addresses a subtle but dangerous bug where TailStrategy::ShiftInwards could overcompute output tiles and reread stale buffer values during vertically fused operations with transposed destinations. This is production-critical for anyone using Halide autoscheduling on mutation-heavy workloads. Meanwhile, the ROCm team is methodically closing deadlock vectors: FBGEMM's compute_amax_and_quantize_kernel [2] had threads hitting early returns before barrier synchronization, a pattern that kills HIP execution without obvious error messages. The same audit caught grid overflow issues in direct_mapped_lxu_cache_lookup_kernel [3], applying canonical caps to prevent silent launch failures. On the ExecutorTorch side, the Arm backend is shipping incremental gains: TOSA dialect ARGMAX support [4], dim mapping helpers for shape-changing operators [5], and adaptive pooling decomposition [6]. TorchTitan shipped a checkpoint compatibility cleanup [7] decoupling from PyTorch distributed state_dict APIs, critical for checkpoint portability, while also reverting a deterministic topk change [8] that broke internal numerics and will reland upstream once semantics stabilize. The MoE sequence parallelism bug fix [9] corrects token index placement when tensor, expert, and sequence parallelism run together, preventing routing misplacement in large multi-axis parallel setups.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] Fix Halide inplace mutation fusion with aliased reads (#186121) pytorch/pytorch
  2. [2] Fix ROCm __syncthreads deadlock in compute_amax_and_quantize_kernel pytorch/FBGEMM
  3. [3] Fix HIP grid overflow in direct_mapped_lxu_cache_lookup_kernel (#5882) pytorch/FBGEMM
  4. [4] Arm backend: Add TOSA dialect ARGMAX op ↗ pytorch/executorch
  5. [5] Arm backend: Add dim mapping helpers ↗ pytorch/executorch
  6. [6] Arm backend: Add adaptive pooling node visitors ↗ pytorch/executorch
  7. [7] [Checkpointer] Remove the dependencies on PyTorch distributed state_dict APIs (#3623) pytorch/torchtitan
  8. [8] Revert "Add deterministic topk for MoE routing" ↗ pytorch/torchtitan
  9. [9] [Bug] Fix MoE SP token combine indices ↗ pytorch/torchtitan

Quick answers

What shipped in PyTorch on June 13, 2026?
PyTorch's Halide backend had a critical inplace mutation fusion bug that could silently corrupt results on aliased reads, and it's not alone: ROCm deadlocks are being systematically hunted across FBGEMM and core compute kernels. In total, 89 commits and 22 pull requests landed.
Who contributed to PyTorch on June 13, 2026?
4 developers shipped this update, including SaoirseARM, AdrianLundell, sanketpurandare, and Matrix-Z97.
What were the notable PyTorch updates?
Fix Halide inplace mutation fusion with aliased reads (#186121), Fix ROCm __syncthreads deadlock in compute_amax_and_quantize_kernel, and Fix HIP grid overflow in direct_mapped_lxu_cache_lookup_kernel (#5882).

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?

We use privacy-friendly analytics (Google Analytics, IP-anonymized) to see which pages help readers. No ads, and we never sell your data. See our Privacy Policy.