[all-commits] [llvm/llvm-project] cb9d4c: [offload-arch] Report gfx1250-strict to match rocm...
A. Cauble via All-commits
all-commits at lists.llvm.org
Fri Sep 18 08:10:18 PDT 2026
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: cb9d4cdf5e415d17aaa54a094939249c15871d2d
https://github.com/llvm/llvm-project/commit/cb9d4cdf5e415d17aaa54a094939249c15871d2d
Author: A. Cauble <accauble at users.noreply.github.com>
Date: 2026-09-18 (Fri, 18 Sep 2026)
Changed paths:
M clang/tools/offload-arch/AMDGPUArchByKFD.cpp
M clang/unittests/offload-arch/OffloadArchTest.cpp
Log Message:
-----------
[offload-arch] Report gfx1250-strict to match rocminfo (#224480)
## Motivation
offload-arch would print gfx1250, but rocminfo reports gfx1250-strict on
revision 0s. We want to print the gfx1250-strict too.
Note: This is based off a [similar PR in
rocm-systems](https://github.com/ROCm/rocm-systems/pull/11639).
## Required Changes
* llvm already can parse the gfx1250 -strict target, so no changes
necessary there.
* offload-arch already printed gfx1250, so just needed to get the ASIC
Revision, which is in bits 25:22 in the capability property.
* If ASIC Revision is 0 and gfx_target_version is gfx1250, then report
"gfx1250-strict"
## Testing
* Tested this on a gfx1250-strict and offload-arch reports correctly.
* Added two unit tests to check for "gfx1250" v "gfx1250-strict"
depending on ASIC revision and guard against accidental parsing of
"capability2"
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list