Skip to content

[ROCm] Bump XLA module pin to pick up the amd_smi migration - #872

Merged
mminutoli merged 1 commit into
rocm-jaxlib-v0.11.1from
users/gulsumgudukbay/bump-xla-module-pin-v0.11.1
Aug 28, 2026
Merged

mminutoli merged 1 commit into
rocm-jaxlib-v0.11.1from
users/gulsumgudukbay/bump-xla-module-pin-v0.11.1

Conversation

@gulsumgudukbay

Copy link
Copy Markdown

Points the XLA archive_override at
ROCm/xla#1144, which migrates the SMI
device queries from rocm_smi to amd_smi. Needed for
TheRock#6852, which removes
librocm_smi64 from the ROCm SDK.

This branch builds with bzlmod (common --enable_bzlmod --noenable_workspace,
since upstream aeff4e4bf), so MODULE.bazel is the live XLA pin and
third_party/xla/revision.bzl is the dormant WORKSPACE path. #867 bumped
revision.bzl only, so the wheel build kept resolving the old pin and TheRock
CI still failed with:

SolibSymlink .../librocm_smi64.so failed: missing input file
@@xla++rocm_configure_ext+local_config_rocm//rocm:rocm_dist/lib/librocm_smi64.so

The previous pin, a530cc3ce3e, was the head of rocm-jaxlib-0.11.1-alpha
before the SMI migration landed there.

Verification

Built against a full ROCm 7.14 SDK with librocm_smi64.so* deleted, resolving
XLA from this archive_override with no --override_module, so the pin itself
is exercised:

  • jax-rocm-pjrt wheel builds; the pinned tarball fetches and its integrity matches.
  • The resulting xla_rocm_plugin.so lists libamd_smi.so.26 as NEEDED, with
    no librocm_smi64 entry.

rocm-jaxlib-v0.11.1 builds with bzlmod, so the live XLA pin is the
archive_override in MODULE.bazel rather than third_party/xla/revision.bzl.
Point it at ROCm/xla rocm-jaxlib-0.11.1-alpha with the SMI migration, so the
wheel build stops requiring librocm_smi64.
@mminutoli
mminutoli merged commit 5e75202 into rocm-jaxlib-v0.11.1 Aug 28, 2026
2 checks passed
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