[Mantic] Compile broken on armhf (cc1 out of memory)

Bug #2060446 reported by Stefan Bader
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
Mantic
Fix Committed
High
Stefan Bader

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://<email address hidden>/T/#u

Stefan Bader (smb)
Changed in linux (Ubuntu Mantic):
assignee: nobody → Stefan Bader (smb)
importance: Undecided → High
status: New → In Progress
Changed in linux (Ubuntu):
status: Triaged → Invalid
importance: High → Undecided
description: updated
Stefan Bader (smb)
Changed in linux (Ubuntu Mantic):
status: In Progress → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure/6.5.0-1021.22 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-azure' to 'verification-done-mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic-linux-azure'.

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-azure-v2 verification-needed-mantic-linux-azure
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.