Skip to content

[release/2.14] Update the apex related commit for the C++20 fix - #3856

Merged
jithunnair-amd merged 1 commit into
release/2.14from
leconcio/apex-cxx20-pin-2.14
Oct 24, 2026
Merged

jithunnair-amd merged 1 commit into
release/2.14from
leconcio/apex-cxx20-pin-2.14

Conversation

@leconcio

@leconcio leconcio commented Oct 21, 2026 •

Copy link
Copy Markdown

Summary

  • Update the apex pin in related_commits for the 2.14 release.
  • Move ROCm/apex release/1.14.0 from a7f8fded to 172d2689, the release/1.14.0 backport of ROCm/apex#341. It is the only commit between the two.
  • Let PyTorch choose the C++ standard when building ops apex#341 removes the hard-coded -std=c++17 from apex's op_builder/builder.py, so PyTorch's cpp_extension picks the C++ standard. PyTorch 2.14+ headers require C++20, so with the old pin the apex ops (amp_C, fused_layer_norm_cuda, ...) fail to build, both when prebuilt and when JIT-compiled on first use.
  • The torchvision and torchaudio pins in related_commits are unchanged.

Apex release commit: 172d26895969173213b2b4c206ed074103efe602

Test plan

🤖 Generated with Claude Code

Move ROCm/apex release/1.14.0 from a7f8fded to 172d2689, the
release/1.14.0 backport of ROCm/apex#341, which lets PyTorch choose the
C++ standard when building apex ops (PyTorch 2.14+ requires C++20).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leconcio

Copy link
Copy Markdown
Author

@leconcio
leconcio marked this pull request as ready for review October 23, 2026 18:57
@jithunnair-amd
jithunnair-amd merged commit d012f28 into release/2.14 Oct 24, 2026
4 checks passed
@jithunnair-amd
jithunnair-amd deleted the leconcio/apex-cxx20-pin-2.14 branch October 24, 2026 00:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants