[Bug 2058606] [NEW] Sync rocm-hipamd 5.7.1-3 (universe) from Debian unstable (main)

Launchpad Bug Tracker 2058606 at bugs.launchpad.net
Wed Mar 27 06:16:13 UTC 2024


You have been subscribed to a public bug by Cory Bloor (slavik81):

Please sync rocm-hipamd 5.7.1-3 (universe) from Debian unstable (main)

This sync requires a FeatureFreeze exception

# Why a new upstream version is necessary

The Ubuntu Noble FeatureFreeze occurred while the ROCm stack on Debian
was transitioning from ROCm 5.2 with clang-15 to ROCm 5.7 with clang-17.
This has left the ROCm stack on Ubuntu Noble with a few problems:

1. Some packages in noble are based on clang-15 while others are based
on clang-17. This mix of versions is not supported upstream and packages
that depend on run-time compilation (such as rocfft) appear to be
entirely broken. Noble will need to move rocm-hipamd to clang-17 to get
all packages on one build toolchain, and the rocm-hipamd version is
closely coupled to the compiler version.

2. The current version of rocm-hipamd (5.2.3) in noble is several years
old and lacks support for modern hardware, such as the Radeon 7000
series of GPUs. As this is a library used for High-Performance Computing
and AI, support for modern hardware is very important.

3. The current rocm-hipamd package depends on the rocm-device-libs
binary package, which is not provided by any source package in noble.
Ubuntu noble needs to complete the transition from rocm-device-libs to
rocm-device-libs-17 and this requires updating rocm-hipamd to a newer
upstream version.

4. The upstream ROCm 5.7.1 version was the last release of the ROCm 5
series. While both ROCm 5.2 and ROCm 5.7 are no longer supported
upstream, there will be a much larger community using ROCm 5.7.
Knowledge sharing within this larger community will be beneficial for
the long-term maintenance of the noble release.

5. The versions of ROCm components included on Ubuntu Noble are very
inconsistent. This FeatureFreeze exception is one of several that I will
be filing in an attempt to get as much of the ROCm stack as possible
onto the upstream 5.7.1 release. The narrower the range of versions, the
better. Ubuntu does not have significant automated testing for the AMD
GPU libraries, so it is safer to use versions that closely correspond to
what upstream and Debian are using (as both do significant testing on
these libraries).

I will be filing FeatureFreeze exceptions requests for rocrand, rocprim,
rocthrust, rocfft, hipfft, rocsparse and hipsparse to get them all onto
5.7.1.

# d/changelog from rocm-hipamd 5.2.3-12 to 5.7.1-3

rocm-hipamd (5.7.1-3) unstable; urgency=medium

  * Add d/p/0035-optional-device-libs-find-package.patch to make
    rocm-device-libs-17 an optional dependency in hip-config.cmake.
  * Add d/p/0036-fix-clangrt-check-for-c.patch to provide consistent
    status information from hip-config.cmake about compiler-rt when
    configuring C and C++ projects.
  * Add d/p/0037-deduplicate-cmake-messages.patch to reduce the verbosity
    of hip-config.cmake.

 -- Cordell Bloor <cgmb at slerp.xyz>  Tue, 26 Mar 2024 00:42:03 -0600

rocm-hipamd (5.7.1-2) unstable; urgency=medium

  * Add d/p/0034-default-to-hip-platform-amd.patch to have hip-config.cmake
    default to building for the AMD platform if hipconfig is not available.
  * d/gbp.conf: ensure use of pristine-tar
  * d/t/hipconfig: enable hipconfig autopkgtests even if KFD is not available
  * d/control: drop dpkg-dev from hipcc depends because it is no longer used
  * d/t/control: require rocminfo (>= 5.7.1~) in autopkgtests to fix failures
    on systems without AMD GPUs

 -- Cordell Bloor <cgmb at slerp.xyz>  Wed, 20 Mar 2024 01:57:15 -0600

rocm-hipamd (5.7.1-1) unstable; urgency=medium

  * Migrate to unstable.

 -- Cordell Bloor <cgmb at slerp.xyz>  Thu, 07 Mar 2024 10:57:55 -0700

rocm-hipamd (5.7.1-1~exp2) experimental; urgency=medium

  * Fix FTBFS on arm64 by conditionally removing use of SSE intrinsics.
  * Fix gcc, clang and g++ autopkgtests.
  * Add d/p/0033-fix-hipconfig-version-githash.patch to fix hipconfig
    version number.

 -- Cordell Bloor <cgmb at slerp.xyz>  Sun, 03 Mar 2024 17:31:02 -0700

rocm-hipamd (5.7.1-1~exp1) experimental; urgency=medium

  * New upstream version 5.7.1
  * Update URLs to reflect consolidation of hipamd, rocclr and
    rocm-opencl into clr.
  * Enable hardening flags.
  * d/libamdhip64-5.symbols: mark hipRegisterTracerCallback as an
    optional symbol. This function is not found in any public header.
    It is an unstable internal interface used by ROCm profiling tools.
  * d/libhiprtc-builtins.so.5: fix lintian warning
    symbols-file-missing-build-depends-package-field
  * Add d/p/0030-disable-immintrin-on-ppc64el.patch to fix build
    on ppc64el.
  * Add d/p/0031-find-package-minimum-policy.patch to fix CMake
    policy warning in find_package(hip).
  * Expand autopkgtests with more build checks (no GPU required).
  * Add d/p/0032-hipcc-compiler-launcher.patch to provide
    HIP_CLANG_LAUNCHER environment variable in hipcc.
    Thanks to Gavin Zhao.

 -- Cordell Bloor <cgmb at slerp.xyz>  Sun, 03 Mar 2024 00:21:39 -0700

rocm-hipamd (5.6.1-1~exp1) experimental; urgency=medium

  * New upstream version 5.6.1
  * Add hipcc upstream tarball
  * Update upstream URLs
  * Update from clang-15 to clang-17 (Closes: #1061208)
  * d/control: drop mlir from build-depends
  * d/control: add graphviz to doc build dependencies (Closes: 1064721)
  * d/rules: disable build tests
  * d/rules: disable rpath rather than patching it out
  * d/hipcc.install: drop install of hip_embed_pch.sh
  * d/libamdhip64-5.symbols: mark profiling API symbols as optional

 -- Cordell Bloor <cgmb at slerp.xyz>  Tue, 27 Feb 2024 02:38:42 -0700

rocm-hipamd (5.2.3-13) unstable; urgency=medium

  * Add debian/clean (Closes: #1046076)

 -- Christian Kastner <ckk at debian.org>  Thu, 14 Sep 2023 15:48:26 +0200

** Affects: rocm-hipamd (Ubuntu)
     Importance: Undecided
         Status: Triaged

-- 
Sync rocm-hipamd 5.7.1-3 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/2058606
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list