Repository navigation
build(tensilelite): assemble gfx950 objects to the gfx950:sramecc+ target id - #14044
Merged
jaopaulolc merged 34 commits intoOct 30, 2026
Merged
jaopaulolc merged 34 commits into
jaopaulolc merged 34 commits into
Conversation
1 task
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## users/jolabega/kfa-rr-mx-1-fixes #14044 +/- ##
=================================================================
Coverage 77.35% 77.35%
=================================================================
Files 2896 2896
Lines 486053 486070 +17
Branches 73475 73478 +3
=================================================================
+ Hits 375957 375975 +18
Misses 85264 85264
+ Partials 24832 24831 -1
*This pull request uses carry forward flags. Click here to find out more.
🚀 New features to boost your workflow:
|
✅ All Policy Checks Passed
📖 Need help? See the Policy FAQ for details on every check and how to fix failures. |
Pre-commit check failed⛔ pre-commit failed Please run locally:
This repo uses |
|
🎉 All checks passed! This PR is ready for review. |
jaopaulolc
marked this pull request as ready for review
October 22, 2026 18:01
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JIRA ID : AIHPBLAS-5262
Motivation
The kernels in
tensilelite/CustomKernels/rocroller/declare a target id the build did not assemble. An AMD GPU is identified not only by its architecture (gfx950, the MI350 series) but by a target id: the architecture plus a tail of hardware feature settings, such asgfx950:sramecc+for a part with error-correcting memory enabled. The assembler compares the whole target id and rejects a mismatch. Of the 90 checked-in kernels, 89 target gfx950 and declare.amdgcn_target "amdgcn-amd-amdhsa--gfx950:sramecc+"while the build assembled them as baregfx950, so none of the 89 could assemble at all. The 90th targets gfx942 and was unaffected.Technical Details
Stacked on #14043.
Every gfx950 artifact is now assembled to the target id its kernels declare. The change keeps the target id and the architecture name on separate channels, which is load-bearing rather than cosmetic:
targetIdOf()in Python andtensilelite_offload_target()in CMake, which append the feature tail. These two feed-mcpu,--offload-arch, the.amdgcn_targetdirective, and the code-object bundle entry.compilerTargetOfandbaseArchName, alongside the bare${arch}. These keep feeding directory names, file names, and the identifier accepted by the--architecture=allow-list.The split is required because the CMake variable
GPU_TARGETSis validated against an allow-list and then stripped by a regular expression into directory names. A feature-qualified value there fails configure, and no path the build produces may contain a colon.The change covers the TensileLite assembly and HIP-source toolchains, the extop generators and their device library, the CMake path that builds the rocRoller custom kernels, and hipBLASLt's own HIP device code by way of
GPU_BUILD_TARGETS.The consequence is that gfx950 code objects are now built
SRAMECC_ONwithXNACK_ANYthroughout, so they will not load on a gfx950 part running with sramecc disabled. That is the accepted trade. rocRoller's just-in-time compilation path already assembled to the target id the device itself reports, through theamd_comgrcompiler library, so this converges the checked-in path with the just-in-time path rather than introducing a new policy.Test Plan
gfx950target id and once againstgfx950:sramecc+, and count successes.GPU_TARGETSandTensileCreateLibrary --architecture=receive the bare name while device code is built for the qualified target id.test_arch_steppings.py: new Python tests over the architecture feature tables, including a drift guard asserting that the CMake and Python feature tables agree, a check that the feature tail never reaches a path or a file name, a check thatGPU_TARGETSitself never grows a feature tail, and a check that every checked-in gfx950 kernel declares the target id the build assembles to.test_custom_kernel_host.pyand the toolchain component characterization suite, as regression cover for the surrounding code.Test Result
Completed evidence:
gfx950target id, 89 of 89 againstgfx950:sramecc+.SRAMECC_ONwithXNACK_ANYand none reports anything else. All 318 load on MI355X.GPU_TARGETSandTensileCreateLibrary --architecture=receivegfx950, while device code is built for target idgfx950:sramecc+.test_arch_steppings.pyadds 16 tests, all passing. The kernel-declaration test asserts a relation over the shipped sources rather than a hardcoded count, so it does not need editing as kernels are added.test_custom_kernel_host.pypasses 54 tests and the toolchain component characterization suite passes 34.Pending: automated GitHub checks have not reported on this branch. The MI355X load check was run locally; no shared CI lane exercises gfx950 code-object loading today.
Submission Checklist
Risk level
Medium. Every gfx950 code object the build produces changes its target id, so a gfx950 part running with sramecc disabled can no longer load them. That is a deliberate narrowing, stated above, and it matches what rocRoller's just-in-time path already did. Architecture names in paths, file names, and the
--architecture=allow-list are unchanged, and the drift guard plus the colon-free path checks are there to catch a regression in that split.