[HIP] configure.py --hip names the AMD libclc target "amdgcn-amd-amdhsa-llvm", but sycl/CMakeLists.txt requires "amdgcn-amd-amdhsa"
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- cmake, cpp
- Domain
- backend, build-system
Research direction
Read configure.py around the libclc_amd_target_names setting and the LLVM runtime target arguments, then compare with the libclc target check in sycl/CMakeLists.txt around lines 619–623. Make the AMD target name consistent so --hip configuration succeeds; verify by reproducing the reported configure command on an AMD HIP setup.
Written by the indexing model from the issue text.
Description
Describe the bug
Configuring with buildbot/configure.py --hip (default --hip-platform AMD) fails, because the script and the SYCL CMake check use different names for the AMD libclc runtime target.
buildbot/configure.py(line 32) setslibclc_amd_target_names = ";amdgcn-amd-amdhsa-llvm"and adds it toLLVM_RUNTIME_TARGETS(lines 93-96, 254-266).sycl/CMakeLists.txt(lines 619-623) requires the plain triple:
if("hip" IN_LIST SYCL_ENABLE_BACKENDS)
if(NOT ("amdgcn-amd-amdhsa" IN_LIST libclc_targets))
message(FATAL_ERROR "HIP support requires building \"libclc\" for the AMDGCN target")
libclc_targets comes from get_targets_building_llvm_runtime(libclc ...), so it contains amdgcn-amd-amdhsa-llvm, the check fails, and configure stops.
To reproduce
On Ubuntu 22.04 x86_64 with ROCm 7.0 (hip-dev, rocm-device-libs) installed:
git clone https://github.com/intel/llvm && cd llvm
git checkout dfcf0080a27749a5c8c73b9d83658593726b01ea # nightly-2026-10-14
python3 buildbot/configure.py --hip --cmake-opt=-DUR_HIP_ROCM_DIR=/opt/rocm
Expected: configure succeeds and builds libclc for AMDGCN.
Actual: configure stops at sycl/CMakeLists.txt:622.
Workaround (later -D options win):
python3 buildbot/configure.py --hip --cmake-opt=-DUR_HIP_ROCM_DIR=/opt/rocm \
"--cmake-opt=-DLLVM_RUNTIME_TARGETS=default;amdgcn-amd-amdhsa;spirv64-unknown-unknown" \
--cmake-opt=-DRUNTIMES_amdgcn-amd-amdhsa_LLVM_ENABLE_RUNTIMES=libclc
With this the toolchain builds, libur_adapter_hip.so is installed, and SYCL programs run correctly on an AMD Instinct MI350X (gfx950).
Suggested fix: use one name in both places: either amdgcn-amd-amdhsa in configure.py, or accept the -llvm variant in the CMake check.
Environment
- OS: Ubuntu 22.04 x86_64
- ROCm 7.0 (apt packages), CMake 3.x, Ninja
- intel/llvm
nightly-2026-10-14(dfcf0080a27749a5c8c73b9d83658593726b01ea); lines unchanged onsyclas of 2026-10-18
Additional context
As far as I can tell no intel/llvm CI job configures with --hip, which may be why this went unnoticed. A related problem in the driver's libspirv lookup comes up after this one is worked around; I'll file it separately. The full build script with both workarounds: https://github.com/checocadena/oneapi-agent-toolkit/blob/main/scripts/build-sycl-hip.sh
- Dominant language
- LLVM
- Stars
- 1.5k
- Forks
- 869
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 194
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from intel/llvm
-
bug Coverity
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
bug Coverity
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
Coverity
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
intel/llvm#23011 · 3 comments ·
Maintainers usually reply within 2 days
-
confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
intel/llvm#23008 · 2 comments ·
Maintainers usually reply within 2 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Fei2411/DeepSeek-Bot#634 ·
-
:Search Relevance/Vectors >test-failure needs:risk Team:Search Relevance
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
elastic/elasticsearch#163668 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Handler accepts zero/negative NNCP_MAX_RETRIES and NNCP backoff values, stalling policies or hot-loopingPossibly taken @NopeCharon claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nmstate/kubernetes-nmstate#1604 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
chore(worker): five module header comments describe the code from before later issues changed itOpenarea:dev U2-later
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bentleypark/aiwatch#1824 ·
Maintainers usually reply within 1 day