This bug is awaiting verification that the linux/6.5.0-33.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060446 Title: [Mantic] Compile broken on armhf (cc1 out of memory) Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: [SRU Justification] Impact: A set of patches from upstream stable was applied to the Mantic 6.5 kernel. The patches reworked the min()/max() macro definitions to allow more flexible input. However this caused the compile to be broken with the solo6x10 driver on armhf because its usage of nested min() and max() results in a pre-compiled file increasing from around 5MB to over 120MB (cc1: out of memory allocating 301930784 bytes after a total of 243818496 bytes). Fix: Revert the following set of patches until a final upstream solution comes up: 21e0901150a6 minmax: relax check to allow comparison between unsigned arguments and signed constants 0410eb4def1f minmax: allow comparisons of 'int' against 'unsigned char/short' 54750fcb53b3 minmax: allow min()/max()/clamp() if the arguments have the same signedness. 8d582aac6cd6 minmax: add umin(a, b) and umax(a, b) Testcase: Compiling the kernel will fail on armhf with those patches applied. So a successful build is testing this. Regression potential: This was not released. Without the new adjustments the min() and max() macros will work as before. --- Upstream discussion: https://lore.kernel.org/all/633b64e2f39e46bb8234809c5595b...@acums.aculab.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
