- Status New
- Percent Complete
- Task Type Bug Report
- Category Packages
- Assigned To No-one
- Operating System pentium4
- Severity Low
- Priority Medium
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Opened by Andreas Baumann - 21.07.2022
Last edited by Andreas Baumann - 21.07.2022
FS#276 - LTO optimization needs to much memory
7234 build 20 0 1353768 1.2g 18020 R 96.1 64.0 4:27.92 lto1-wpa
xf86-video-intel (this is not exactly a huge package, but maybe the
included X libraries are?)
We lost it on i486 already (because it doesn’t work with newer gcc, or at least
I didn’t investigate how to make it work).
I suggest to get rid of LTO completely.
The problem is patching all the options=(lto), –enable-lto/ –without-lto -D b_lto=tru
etc. which easily creates a maintainance nightmare.
Maybe an easier way to go is to have them similar to the ‘lib32-’ stripping
in the main build scripts or hooks? Downstream this might create
trouble tough, as the build systems are different..
Upstream has options=(lto) support, but it doesn’t seen helping here as packages
need local flags everywhere..
An alternative is to use 486 chroot for building software which needs to much memory
on the 486 VMs (having other nasty effects due to failed hardware property probing -
the very reason why we use VMs in the first place).
On pentium4 I get with the same module now on a machine with 64GB RAM:
virtual memory exhausted: Operation not permitted
options=(!lto)
helps
LTO also just uses parallel processes ad abundance, which we have to tame again
in order not to kill build machines..