AMD and Intel merge their x86 PyTorch optimizations into oneDNN as one default path; AMD folds in ZenDNN and joins the UXL Foundation

Why it matters

【Key points】

AMD and Intel said on Oct 20 they will combine their x86 CPU optimizations for PyTorch in one open-source library, oneDNN, giving developers a single software path across both companies' processors.

1. What changes: both have aligned on oneDNN as the default open-source library for x86 acceleration in PyTorch. AMD is folding its ZenDNN optimizations into oneDNN while continuing to tune for its own chips. oneDNN is governed by the Unified Acceleration (UXL) Foundation, which AMD has joined as a steering member.

2. Origin: the move follows a recommendation from the x86 Ecosystem Advisory Group the two companies take part in.

3. Next: the companies are also working on AI Compute Extensions (ACE), a new x86 instruction set for matrix multiplication, to be brought into PyTorch through future oneDNN updates.

4. Red Hat welcomed the move as a step against fragmentation. The announcement gives no performance figures or timeline.

【Verifiable】

AMD announcement: https://newsroom.amd.com/news/amd-intel-collaborate-simplify-ai-development-on-x86-cpus-pytorch/

【Our read】

1. Until now AMD and Intel each kept separate CPU optimization libraries for PyTorch, so developers and framework maintainers had to support both. One upstream path mainly cuts maintenance work; it does not by itself make models faster.

2. It fits the same trend as Google's TorchTPU and Amazon's TorchNeuron: hardware vendors competing to run PyTorch code unchanged.

3. ACE is described as a next-generation x86 instruction set, with no word on which chips will support it or when, so any real gain for CPU inference depends on future hardware and oneDNN releases.