bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/22831] ld causes massive thrashing if object files are not fully


From: luke.leighton at gmail dot com
Subject: [Bug ld/22831] ld causes massive thrashing if object files are not fully memory-resident: new algorithm needed
Date: Sat, 23 Jul 2022 10:08:15 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=22831

--- Comment #32 from luke.leighton at gmail dot com ---
(replying privately)

dealing with this one was deeply unpleasant. i gave up as people were not
listening.  i refer people to it frequently whenever they encounter serious
build problems.

the torture demo is dead easy to autogenerate programs that crash both ld and
gold, for both 32 and 64 bit. for 64 bit just keep increasing the parameters
until programs exceed 16 gbytes in size and in some cases they won't even link
at all.

there are multiple complaints by distro builders that their 128 GB and 256 GB
build farms actually kernel panic if they happen to accidentally have e.g.
firefox, libreoffice and other massive linking occur simultaneously, due to
thrashing.  with 128 GB of RAM!

i have had my very expensive laptop hit 1,200 loadavg due to this problem, it
nearly lost me a year's work and took 25 minutes to get the cursor to move so i
could hold down Ctrl-C and terminate the build.

it's exacerbated significantly by debug builds.

l.





On July 23, 2022 3:37:03 AM GMT+01:00, amodra at gmail dot com
<sourceware-bugzilla@sourceware.org> wrote:
>https://sourceware.org/bugzilla/show_bug.cgi?id=22831
>
>Alan Modra <amodra at gmail dot com> changed:
>
>           What    |Removed                     |Added
>----------------------------------------------------------------------------
>           Severity|critical                    |enhancement
>             Status|WAITING                     |NEW
>           Priority|P1                          |P3
>
>--- Comment #31 from Alan Modra <amodra at gmail dot com> ---
>Putting priority and severity back where they belong.
>
>-- 
>You are receiving this mail because:
>You reported the bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]