-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rocm-runtime is still using gcc, is about to become broken by gcc13 #271943
Comments
I recommend you guys merge a PR which pins |
Also thank you all for the awesome hard work you did to make this happen. I was totally shocked when I was able to get 8*MI25s to run Falcon-180B in llama.cpp with only a few days of effort. Obviously that's because you folks had already put in months of work to make it so smooth... |
Unfortunately, I'm aware. I was working on making
It's likely all the way to the root - ROCm LLVM. It has a GCC backend which is used. Any chance you could give me the error log for |
Ah, that's actually somewhat of a relief. At least the problem is known. Log is attached. I'm happy to test fixes; I have plenty of compute. After the new year I will be working on making the buildfarm available to other projects; you'll be on the shortlist if you're interested. |
Also if you need to get my attention I hang out in |
Okay, this is
I appreciate that, when I put the PR through I might request that you do a |
Actually, I think I may take your suggestion and just pin a GCC version until a new ROCm release. |
Try reverting this on a future ROCm release. Addresses: NixOS#271943
Try reverting this on a future ROCm release. Addresses: #271943
Fixed by #271954 |
Heads up: even though it tries to
overrideCC
withclang
, ourrocm-runtime
expression still usesgcc
for a ton of stuff.Try changing
default-gcc-version
inpkgs/top-level/all-packages.nix
to13
and you'll see the breakage. I'm about to mergewhich does this, and it's going to break
rocmPackages
. I tried to fix it, but the problem is very deep: you guys think you're using only clang, but in fact you're not.Wanted to give you a heads-up.
cc: @lovesegfault @Madouura @Flakebi
The text was updated successfully, but these errors were encountered: