hipBLASLt icon indicating copy to clipboard operation
hipBLASLt copied to clipboard

[Issue]: 6.4.0 can break creation of tensile libraries in builds that use Unix Makefiles generator

Open justinkb opened this issue 8 months ago • 1 comments

Problem Description

I ran into this on NixOS with a ton of custom stuff I have on top of nixos-24.11 nixpkgs branch and cherry-picks from nixos-unstable, so this will probably be not easy to track down exactly.

Just wanted to report the issue since it was quite weird that when I changed the build to use ninja, it just worked all of a sudden (after having tried literally dozens of other things to fix it first)

Disregard the rocm 6.2.3 version, the dropdown menu on the bug report wouldn't allow me to select anything higher than that.

Operating System

NixOS 24.11

CPU

7950X3D

GPU

AMD Radeon RX 7900 XTX

Other

No response

ROCm Version

ROCm 6.2.3

ROCm Component

No response

Steps to Reproduce

No response

(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support

No response

Additional Information

No response

justinkb avatar Apr 27 '25 19:04 justinkb

Hi @justinkb. Internal ticket has been created to investigate this issue. Thanks!

ppanchad-amd avatar Apr 28 '25 15:04 ppanchad-amd

Hey @justinkb what error did the build process emit when it failed like you described?

christian-heusel avatar May 09 '25 12:05 christian-heusel

Hey @justinkb what error did the build process emit when it failed like you described?

hi, it didn't produce any errors, it just totally skipped the step. which is why I only noticed it at runtime. It only created the one hipblasltTransform.hsaco (IIRC) and nothing else during the early build process and then it made libhipblaslt.so

justinkb avatar May 09 '25 14:05 justinkb

Hi @justinkb, NixOS isn't currently among the operating systems we support. Please take a look at the ROCm compatibility matrix for guidance. Could you try reproducing the issue on Ubuntu 22 or another supported OS?

taylding-amd avatar May 13 '25 15:05 taylding-amd

Hi, this issue will be closed now due to inactivity. Please feel free to reopen it or ask follow-up questions should further assistance be required. Thanks!

taylding-amd avatar Jun 11 '25 19:06 taylding-amd