Public bug reported: [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 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Mantic) Importance: High Assignee: Stefan Bader (smb) Status: In Progress ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu) Importance: High => Undecided ** Description changed: [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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060446 Title: [Mantic] Compile broken on armhf (cc1 out of memory) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
