Build gfx125X hotswap stack with PR6346 amd-llvm

[ammarwa]

Summary

This branch captures the current gfx125X hotswap validation combo with the compiler/amd-llvm gitlink corrected to match the PR6346 hotswap chain.

Key source state:

• TheRock base: 5db05fe
• compiler/amd-llvm: 4fe37e2ab0cb24b34b135b12f6b93d84394fde7b
• rocm-systems: 8e1ee991ebea976c5a473624482538f5628af33c
• rocm-libraries: 4da814d03513e397f1c1d66047b00669673f7ec1

This intentionally preserves the current hotswap combo and only fixes the prior compiler/amd-llvm mismatch against PR6346.

PR7869 Exclusion Gate

The regenerated build must not include ROCm/rocm-systems#7869. The build evidence records this gate:

cd <TheRock source>/rocm-systems
git fetch origin pull/7869/head:refs/remotes/origin/pr-7869-head || true
git merge-base --is-ancestor c12ef1ad8bf9a6ccc6f3fc57de0bda6c7f978887 HEAD && echo BAD_INCLUDED || echo OK_NOT_INCLUDED

Observed result: OK_NOT_INCLUDED.

Build/Validation

A corrected gfx125X runtime tarball and matching tests tarball are being regenerated from this source combo. Publication and dashboard evidence will be attached in the validation handoff once packaging completes.

[therock-pr-bot]

❌ PR Check — Action Required

Check	Status	Details
🌿 Branch Name	✅ Pass	—
📝 PR Title/Description	❌ Fail	Error: Title does not follow Conventional Commits style. Expected: start with a valid type (feat, fix, docs, …). Desired format: type(optional-scope): short description ─── Error: PR description must reference a JIRA ID, ISSUE ID, or a GitHub closing keyword. Expected: include a JIRA ID / ISSUE ID line (separator : or -, or omitted; value may be a JIRA key, a number with/without #, or a link), OR a closing keyword + issue reference. Accepted examples: • JIRA ID : TESTAUTO-6039 • JIRA ID - #330 • JIRA ID #330 • ISSUE ID : TESTUTO-3334 • ISSUE ID #3334 • ISSUE ID - TESTAUTO-3433 • ISSUE ID : https://github.com/<org_name>/<repo_name>/issues/1234 • Closes #10 • Fixes octo-org/octo-repo#100 • Resolves: #123 • #123 • https://github.com/<org_name>/<repo_name>/issues/123 Current: no valid JIRA/ISSUE/closing-keyword reference found
⛔ Forbidden Files	✅ Pass	—
🧪 Unit Test	✅ Pass	PR does not contain code files — Unit Test auto-passed
🔎 pre-commit	⏳ Pending	⏳ Still running…
🚫 Draft PR	🔜 To Be Enabled	—
🚩 Feature Flag	🔜 To Be Enabled	—
📊 Code Coverage	🔜 To Be Enabled	—

⚠️ 1 policy check(s) failed. Please address the issues above before this PR can be Reviewed.

🚫 Please fix the failed policies

• ❌ PR Title/Description

The Not ready to Review label was added to this PR. Once all policies pass, the label is removed automatically.

📖 Need help? See the Policy FAQ for details on every check and how to fix failures.

[therock-pr-bot]

🚫 Please fix the failed policies before requesting reviews.

The following policy checks failed:

• ❌ PR Title/Description

The Not ready to Review label has been added to this PR.
Once all policies pass, the label will be removed automatically.

[schundu007]

❌ PR Gate — Gate failing

Classification: mixed · Labels: Not ready to Review

	Category	Status	Matched check
⚪	lint	missing	no matching check
❌	tests	failure	Linux::release / Build DEB Packages +28
⚪	docs	missing	no matching check
⚪	license	missing	no matching check

Runner recommendation: gpu 🖥️ GPU — Mixed changes — use GPU runner to be safe

_{Updated by GitPulse · 2026-07-07 04:32 UTC}

[marbre]

This doesn't seem it should target main. What is the purpose of this PR?