Skip to content

[release/2.11] Bump AOTriton pin 0.12.50tp2 -> 0.13b to fix GCC build break#3472

Open
ethanwee1 wants to merge 1 commit into
release/2.11from
bump-aotriton-0.13b-2.11
Open

[release/2.11] Bump AOTriton pin 0.12.50tp2 -> 0.13b to fix GCC build break#3472
ethanwee1 wants to merge 1 commit into
release/2.11from
bump-aotriton-0.13b-2.11

Conversation

@ethanwee1

@ethanwee1 ethanwee1 commented Jul 23, 2026

Copy link
Copy Markdown

Part of the release/2.11 wheel-build fix stack tracked by #3477 (all pieces validated together in one combined green build). Jira: https://amd-hub.atlassian.net/browse/AIPYTORCH-827

Why

The manylinux wheel build fails compiling torch_hip against the AOTriton 0.12.50tp2 headers under GCC 11 (gcc-toolset-11):
https://rocm-ci.amd.com/blue/organizations/jenkins/pytorch-manylinux-wheel-builder_rel-7.2/detail/pytorch-manylinux-wheel-builder_rel-7.2/526/pipeline/556/

In file included from /pytorch/torch/include/aotriton/flash.h:7,
                 from .../ATen/native/transformers/hip/sdp_utils.cpp:31:
/pytorch/torch/include/aotriton/config.h:27:22: error: expected identifier before '__attribute__'
   27 | #define AOTRITON_API __attribute__ ((visibility ("default")))
/pytorch/torch/include/aotriton/v2/cpp_tune.h:26:104: error: expected initializer before ':' token
   26 | enum [[deprecated(...)]] AOTRITON_API CppTuneSpecialKernelIndex : int {
ninja: build stopped: subcommand failed.

The 0.12.50tp2 preview package applies the AOTRITON_API visibility attribute (__attribute__((visibility("default")))) to enum/struct declarations in the deprecated V2 API headers. GCC does not accept a visibility attribute in that position on an enum with a fixed underlying type, so the build fails (clang tolerates it). The 0.13b package used by release/2.12 and main builds cleanly with the same toolchain.

Fix

Validation build: https://rocm-ci.amd.com/blue/organizations/jenkins/pytorch-manylinux-wheel-builder_rel-7.2/detail/pytorch-manylinux-wheel-builder_rel-7.2/528/pipeline
http://compute-artifactory.amd.com/artifactory/compute-pytorch-rocm/compute-rocm-rel-7.2/93/
Bump the AOTriton pin 0.12.50tp2 -> 0.13b (matching release/2.12 and main), updating __AOTRITON_VER, __AOTRITON_CI_COMMIT, and the runtime/image SHA256 lists.

… break

The manylinux wheel build failed compiling torch_hip against the AOTriton
0.12.50tp2 headers under GCC 11 (gcc-toolset-11):

    In file included from /pytorch/torch/include/aotriton/flash.h:7,
                     from .../ATen/native/transformers/hip/sdp_utils.cpp:31:
    /pytorch/torch/include/aotriton/config.h:27:22: error: expected identifier before '__attribute__'
       27 | #define AOTRITON_API __attribute__ ((visibility ("default")))
    /pytorch/torch/include/aotriton/v2/cpp_tune.h:26:104: error: expected initializer before ':' token
       26 | enum [[deprecated(...)]] AOTRITON_API CppTuneSpecialKernelIndex : int {
    ninja: build stopped: subcommand failed.

The 0.12.50tp2 preview package applies the AOTRITON_API visibility attribute
(__attribute__((visibility("default")))) to enum/struct declarations in the
deprecated V2 API headers. GCC does not accept a visibility attribute in that
position on an enum with a fixed underlying type, so the build fails (clang
tolerates it). The 0.13b package used by release/2.12 and upstream main builds
cleanly with the same toolchain.

Bump the AOTriton pin to 0.13b (matching release/2.12 and main), updating the
version, CI commit, and runtime/image SHA256 lists accordingly.
@ethanwee1
ethanwee1 force-pushed the bump-aotriton-0.13b-2.11 branch from 236a23c to 632e5f7 Compare July 23, 2026 15:40
@jithunnair-amd

Copy link
Copy Markdown
Collaborator

@ethanwee1 Please include a link to a failed build that shows the error, and a Validation build, when available.

@ethanwee1
ethanwee1 marked this pull request as ready for review July 23, 2026 17:41
@xinyazhang

Copy link
Copy Markdown

Or you can wait for 0.13.50tp that will be release later this afternoon. @ethanwee1 @jithunnair-amd

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.

3 participants