https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #35 from Luke Kenneth Casson Leighton ---
On Sat, Jul 23, 2022 at 3:04 PM amodra at gmail dot com
wrote:
> And "new algorithm needed" is really saying "rewrite the linker".
i mention this very early on in this bugreport: back in
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #30 from Luke Kenneth Casson Leighton ---
cross-reference here, raised priority critical bug in the debian bugtracker
as well:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919882
--
You are receiving this mail because:
You a
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #29 from Luke Kenneth Casson Leighton ---
i tried the same massive 6GB link as was carried out under an i386 (32-bit)
chroot. this time both of them succeeded. ld-bfd with --no-keep-memory
succeeded as before with a warning, usin
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #28 from Luke Kenneth Casson Leighton ---
(In reply to Luke Kenneth Casson Leighton from comment #27)
> ld-bfd - with "--no-keep-memory" - only requires 750 MB of resident RAM, to
> link the exact same 6GB executable.
(and aside
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
Luke Kenneth Casson Leighton changed:
What|Removed |Added
Attachment #11522|0 |1
is obsolete|
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #26 from Luke Kenneth Casson Leighton ---
(In reply to Ian Lance Taylor from comment #25)
> When using gold the key options are --no-mmap-output-file
> --no-map-whole-files --no-keep-files-mapped. Can you confirm that those
> opti
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #24 from Luke Kenneth Casson Leighton ---
hiya nick, thanks for trying out the torture program. basically the
parameters there generate a 6.1mb object file (with gcc 7.3), and 3000x
that equals an 18 gbytes executable.
so, it's p
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #22 from Luke Kenneth Casson Leighton ---
Created attachment 11522
--> https://sourceware.org/bugzilla/attachment.cgi?id=11522&action=edit
repro test case
attached is a test file that can generate a Makefile and associated
heade
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
Luke Kenneth Casson Leighton changed:
What|Removed |Added
Priority|P2 |P1
Severity|
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #21 from Luke Kenneth Casson Leighton ---
to emphasise that this is strategically becoming an absolutely critical bug:
https://lists.debian.org/debian-devel/2019/01/msg00081.html
here it has been reported that even when using -Wl,
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #20 from Luke Kenneth Casson Leighton ---
ok so i spoke to dr stallman a couple of weeks ago, and he confirmed that code
that is near-identical to that which i described in the very first comment of
this bugreport was REMOVED some
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #19 from Luke Kenneth Casson Leighton ---
(In reply to H.J. Lu from comment #18)
> (In reply to Luke Kenneth Casson Leighton from comment #17)
> > https://issues.guix.info/issue/33676
> >
> > so we have a successful report that th
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #17 from Luke Kenneth Casson Leighton ---
https://issues.guix.info/issue/33676
so we have a successful report that the advised option helps.
please note: the advised option is **NOT** repeat **NOT** a solution.
destroying all of
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #16 from Luke Kenneth Casson Leighton ---
the following came up in a debian discussion and is copied here:
Florian Weimer
8:31 PM (14 minutes ago)
to Luke, Steve, ARM, debian-release, debian-admin, team, debian-gcc,
debian-glibc
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #15 from Luke Kenneth Casson Leighton ---
(In reply to H.J. Lu from comment #14)
> (In reply to Luke Kenneth Casson Leighton from comment #13)
> > i have 16 GB of DDR4 2400 mhz RAM on my laptop... and because when
> > that system
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #13 from Luke Kenneth Casson Leighton ---
On Wed, Mar 14, 2018 at 12:26 PM, hjl.tools at gmail dot com
wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=22831
>
> --- Comment #12 from H.J. Lu ---
> (In reply to Luke Kennet
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #11 from Luke Kenneth Casson Leighton ---
(In reply to H.J. Lu from comment #10)
> What is your main issue?
i do not (personally) have an issue, hj. this is a flaw that is
independent of me (personally).
do you mean to ask,
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #9 from Luke Kenneth Casson Leighton ---
(In reply to H.J. Lu from comment #8)
> Have you tried users/hjl/pr18028 branch?
no, hj, i have not, because it is a fix for a 32-bit system,
not a 64-bit system. what do you need to know
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #7 from Luke Kenneth Casson Leighton ---
hi hjl,
so how are you getting on with analysing this problem? is there anything
that is unclear that i can assist you with understanding?
--
You are receiving this mail because:
You are
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #6 from Luke Kenneth Casson Leighton ---
(In reply to H.J. Lu from comment #5)
> Please read my suggestion again and follow it to the letter.
sorry, hjl, i appreciate you're busy so are providing extremely
short responses: please
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #4 from Luke Kenneth Casson Leighton ---
(In reply to H.J. Lu from comment #3)
> Please try users/hjl/pr18028 branch at
>
> https://github.com/hjl-tools/binutils-gdb
hi hjl, i will point some people at this, it may be some time
a
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #2 from Luke Kenneth Casson Leighton ---
hi HJ, thanks for that advice - bear in mind that i am not actually
directly involved in any of the projects that are experiencing these
insane levels of thrashing. we (you and i) are there
: UNCONFIRMED
Severity: normal
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: lkcl at lkcl dot net
Target Milestone: ---
ok so this is quite complex / comprehensive, as it's a performance-related
bug that is s
23 matches
Mail list logo
