[Issue]: tags rocm-7.14 and rocm-10.0 call rocm_add_version_resource, which is not in any released rocm-cmake
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 333
- Forks
- 150
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 54
Description
Problem Description
rocm_add_version_resource added to rocm-cmake with commit 33541cd (2026-04-17, PR #285), git tag --contains returns empty, so it is not in therock-10.0, therock-7.14 or rocm-7.2.4. MIGraphX calls it at src/CMakeLists.txt:184 on tag rocm-10.0 (becdb3d) and :181 on rocm-7.14 (4bcfe75)
obviously disregard ROCM version I had to fill in, the dropdown menu doesn't go above ROCM 6
Operating System
NixOS 26.05
CPU
7950X3D
GPU
AMD Radeon RX 7900 XTX
Other
No response
ROCm Version
ROCm 6.0.0
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start at src/CMakeLists.txt around lines 181-184 and inspect how the rocm_add_version_resource call depends on rocm-cmake. Check the rocm-10.0 and rocm-7.14 tags against the released rocm-cmake versions listed in the report. Done means the affected tags no longer rely on a command absent from their released build dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100