You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I already reported the issue to @searlmc1, it seems like there was a feature backport to this tree from LLVM 19 for 6.1.2, while 6.1.x originally was planned to use LLVM 17 API. This causes issues for anyone using upstream LLVM 17 instead of the ROCm LLVM tree.
It's pretty easy to workaround, because anyone using upstream llvm can just revert 96b2ba3
I just wanted to report this for awareness, and to document it for people using upstream LLVM looking for workarounds. This likely will be an issue for a few releases, since LLVM 19 hasn't even branched yet at this time.
Operating System
All
CPU
Any
GPU
AMD Instinct MI300X
ROCm Version
ROCm 6.1.0
ROCm Component
llvm-project, ROCm-Device-Libs
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Problem Description
I already reported the issue to @searlmc1, it seems like there was a feature backport to this tree from LLVM 19 for 6.1.2, while 6.1.x originally was planned to use LLVM 17 API. This causes issues for anyone using upstream LLVM 17 instead of the ROCm LLVM tree.
It's pretty easy to workaround, because anyone using upstream llvm can just revert 96b2ba3
I just wanted to report this for awareness, and to document it for people using upstream LLVM looking for workarounds. This likely will be an issue for a few releases, since LLVM 19 hasn't even branched yet at this time.
Operating System
All
CPU
Any
GPU
AMD Instinct MI300X
ROCm Version
ROCm 6.1.0
ROCm Component
llvm-project, ROCm-Device-Libs
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: