Hi Cordell,
On 22/11/2024 20:40, Cordell Bloor wrote:
Hi Emilio,
On 2024-11-22 08:52, Emilio Pozuelo Monfort wrote:
> rocm-compilersupport: Please upgrade build-dep to llvm/clang 18 or 19
> rocm-device-libs: Please upgrade build-dep to llvm/clang 18 or 19
> rocm-hipamd: Please upgrade build-dep to llvm/clang 18 or 19
> rocr-runtime: Please upgrade build-dep to llvm/clang 18 or 19
Any chance we can get these bugs addressed for trixie? That should only leave
us one blocker to remove llvm 17 and release with llvm 18 and 19, which we'd
like to do.
The ROCm 6.2 release is based on llvm 18, so this bug would be resolved by
updating these packages to the latest current upstream release. I would also
very much like to move to llvm 18 for Trixie because the --offload-compress
option added in that release would decrease the size-on-disk of the ROCm
libraries to something like ~1/10th their current size.
The Debian ROCm Team is doing the update to ROCm 6.2 in two stages. First, we
will update from ROCm 5.7 to ROCm 6.1, then we then will update from ROCm 6.1 to
ROCm 6.2. It's being done this way so that we can more easily identify whether
it was the runtime update or the compiler update responsible for any breakages
that are introduced.
rocm-compilersupport and rocm-device-libs have been superseded by rocm-llvm,
which is currently in the NEW queue [1]. Whether we will be able to make it to
ROCm 6.2 in time for Trixie is an open question. At our current pace, it's
looking unlikely.
Thanks for the update. After your email, I asked ftp-masters about rocm-llvm,
and it got accepted. With that done, how's the update to 6.1 coming along? Do
you think it can happen soon?
Cheers,
Emilio
