{2025.06}[GCCcore/14.2.0] Adding ROCm-LLVM v19.0.0 /w ROCm 6.4.1#1473
{2025.06}[GCCcore/14.2.0] Adding ROCm-LLVM v19.0.0 /w ROCm 6.4.1#1473casparvl wants to merge 11 commits intoEESSI:mainfrom
Conversation
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws on:arch=zen2 for:arch=x86_64/amd/zen2,accel=amd/gfx90a |
|
New job on instance
|
|
bot:cancel jobid:148423 |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws on:arch=zen2 for:arch=x86_64/amd/zen2,accel=amd/gfx90a |
|
New job on instance
|
And then later: Work to be done I guess... |
|
bot:cancel jobid:148424 |
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws on:arch=zen2 for:arch=x86_64/amd/zen2,accel=amd/gfx90a |
|
New job on instance
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws on:arch=x86_64/amd/zen3 for:arch=x86_64/amd/zen3,accel=amd/gfx90a |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
See https://github.com/ROCm/ROCm/blob/rocm-6.4.1/.azuredevops/components/llvm-project.yml |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws on:arch=aarch64/generic for:arch=aarch64/generic,accel=amd/gfx90a |
|
New job on instance
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws on:arch=aarch64/generic for:arch=aarch64/generic,accel=amd/gfx90a |
|
New job on instance
|
|
|
Considering the function is defined, but not used - and considering it seems to be the function body that causes issues - maybe the bug wasn't that the declaration was removed, but maybe the bug was that the function implementation wasn't also removed? |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws on:arch=aarch64/generic for:arch=aarch64/generic,accel=amd/gfx90a |
|
New job on instance
|
|
Seems like it contains more of these functions where there's only a definition, no declaration... We can try to clean up a couple more. But it might be good to have another look how the ROCm-LLVM repo ended up in this situation - my bet is that upstream LLVM was fine... |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws on:arch=aarch64/generic for:arch=aarch64/generic,accel=amd/gfx90a |
|
New job on instance
|
|
@zerefwayne something wrong with the patch file... |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws on:arch=aarch64/generic for:arch=aarch64/generic,accel=amd/gfx90a |
|
New job on instance
|
|
There we go again... |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws on:arch=aarch64/generic for:arch=aarch64/generic,accel=amd/gfx90a |
|
New job on instance
|
|
|
If we want to look into the configuration flags: this is the current configure command |
I checked the suggested solution, and it completely misses the point. In their CI, they specify: Of course you don't get the ARM failures that way, because you're not supporting ARM targets that way. And of course, that is not the solution we want. |
Just going to try something here, see what we are still missing for AMD GPU support...