Re: Simplifying ROCm compiler upgrades
Hi Cory,
sounds reasonable to me, with one comment (see below).
How do you plan to test this? In case we both missed something. Breaking
up circular dependencies and renames always have the potential to break
something.
With testing, I mean install-time, as in user A has a trixie or forky
system, and runs apt-get upgrade, possibly not even on a ROCm component
but something that uses one.
On 2025-10-17 21:52, Cordell Bloor wrote:
> 5. Propose src:llvm-toolchain-rocm with the full AMD LLVM fork (i.e.,
> amdclang++). It would provide hipcc-rocm, amd-device-libs-rocm, clang-
> rocm, etc. If we decide to switch to it, we can update src:rocm-llvm-
> defaults to make the change.
I find the -rocm suffix is pretty confusing; hipcc-rocm sounds
tautological. Sadly, I don't have any better ideas.
Best,
Christian
Reply to: