torch.compile

Headlines · 2

1. Oct 19
   PyTorch Helion taps Nvidia CompileIQ to tune ptxas compiler controls

   A PyTorch blog post says Helion's kernel autotuner previously searched only tile shapes, warp counts, pipeline stages and memory access strategy, and can now also search ptxas compiler controls such as register allocation policy, fine-grained instruction scheduling and code-generation heuristics through Nvidia's CompileIQ, packaging results as portable Advanced Control Files (ACFs). In one example on a fixed, ahead-of-time-tuned NVFP4 GEMV kernel, an evolutionary CompileIQ search over eight generations with a pool of 15 candidates on GB200 cut execution time from 0.0971 ms to 0.0928 ms, a 1.047x (4.7%) speedup; the post stresses the gain is workload-specific and depends on shapes and architecture. Helion is open source under the PyTorch Foundation, while CompileIQ is proprietary but free to use under Nvidia's license, and the ACF files it produces are freely distributable.

   PyTorch Blog · 🔥 0
2. Oct 8
   torch-spyre brings IBM Spyre in as a native PyTorch device

   IBM's torch-spyre team published a PyTorch blog post describing how it made Spyre, IBM's dataflow AI accelerator for inference, a native PyTorch device. The integration uses PrivateUse1 registration to give Spyre a device identity named "spyre", then maps PyTorch's allocator, stream, event and Inductor compiler abstractions onto Spyre runtime constraints such as ordered queues of typed operations, separate compute and data-movement pipelines, and ahead-of-time compiled programs with fixed layouts. IBM says this gives one path for eager and compiled execution, keeps tensors resident on device="spyre", and cuts launch overhead; no performance or benchmark figures are given, and the source text is truncated near the end.

   PyTorch Blog · 🔥 0

Experience and discussion from the community

Share my torch.compile experienceAsk about torch.compile