[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: |
lkcl at lkcl dot net |
Subject: |
[Bug ld/22831] ld causes massive thrashing if object files are not fully memory-resident: new algorithm needed |
Date: |
Fri, 29 Jun 2018 19:53:19 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #16 from Luke Kenneth Casson Leighton <lkcl at lkcl dot net> ---
the following came up in a debian discussion and is copied here:
Florian Weimer <address@hidden>
8:31 PM (14 minutes ago)
to Luke, Steve, ARM, debian-release, debian-admin, team, debian-gcc,
debian-glibc
* Luke Kenneth Casson Leighton:
> that is not a surprise to hear: the massive thrashing caused by the
> linker phase not being possible to be RAM-resident will be absolutely
> hammering the drives beyond reasonable wear-and-tear limits. which is
> why i'm recommending people try "-Wl,--no-keep-memory".
Note that ld will sometimes stuff everything into a single RWX segment
as a result, which is not desirable.
Unfortunately, without significant investment into historic linker
technologies (with external sorting and that kind of stuff), I don't
think it is viable to build 32-bit software natively in the near
future. Maybe next year only a few packages will need exceptions, but
the number will grow with each month. Building on 64-bit kernels will
delay the inevitable because more address space is available to user
space, but that's probably 12 to 18 month extended life-time for
native building.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug ld/22831] ld causes massive thrashing if object files are not fully memory-resident: new algorithm needed,
lkcl at lkcl dot net <=