https://sourceware.org/bugzilla/show_bug.cgi?id=22831
Sam James changed:
What|Removed |Added
CC||sam at gentoo dot org
--
You are
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #38 from Giovanni Lostumbo ---
I contacted Dr.(h.c) Richard Stallman the other day to inquire which of
original GNU ld versions he wrote.
He replied (spelling errors included and annotated with "[sic]" by me),
"The original
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #37 from Giovanni Lostumbo ---
Created attachment 14339
--> https://sourceware.org/bugzilla/attachment.cgi?id=14339=edit
ld.c 3-29-1991 reads object files and libraries 2x to minimize memory
--
You are receiving this mail
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
Giovanni Lostumbo changed:
What|Removed |Added
CC||giovanni.lostumbo at gmail dot
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
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #34 from Alan Modra ---
I'll note that the priority and severity fields in bugzilla are primarily for
the use of maintainers, or at least that should be the way they are treated.
They are not for bug reporters to say "this bug is
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #33 from luke.leighton at gmail dot com ---
that was supposed to be a private reply, bugzilla masked the email address
"amodra ". the comment still stands though. i apologise for the
toppost context.
--
You are receiving this
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.
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
Alan Modra changed:
What|Removed |Added
Severity|critical|enhancement
Status|WAITING
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
Dmitry Nezhevenko changed:
What|Removed |Added
CC||dion at inhex dot net
--
You
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
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,
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
>
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
Ian Lance Taylor changed:
What|Removed |Added
CC||ian at airs dot com
--- Comment
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
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
Nick Clifton changed:
What|Removed |Added
CC||nickc at redhat dot com
--- Comment
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=edit
repro test case
attached is a test file that can generate a Makefile and associated
header and
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
Luke Kenneth Casson Leighton changed:
What|Removed |Added
Priority|P2 |P1
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
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
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #18 from H.J. Lu ---
(In reply to Luke Kenneth Casson Leighton from comment #17)
> https://issues.guix.info/issue/33676
>
> so we have a successful report that the advised option helps.
>
Have you tried my users/hjl/pr18028
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,
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 #14 from H.J. Lu ---
(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 goes into swap (it has an NVMe) its loadavg goes over 120
> and
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
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #12 from H.J. Lu ---
(In reply to Luke Kenneth Casson Leighton from comment #11)
> (In reply to H.J. Lu from comment #10)
> there are two issues:
>
> 1. 32-bit system
> 2. 64-bit system
>
> both 32-bit and 64-bit are
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
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #8 from H.J. Lu ---
(In reply to Luke Kenneth Casson Leighton from comment #7)
> 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?
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:
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #5 from H.J. Lu ---
(In reply to Luke Kenneth Casson Leighton from comment #4)
> (In reply to H.J. Lu from comment #3)
> > Please try users/hjl/pr18028 branch at
> >
> > https://github.com/hjl-tools/binutils-gdb
>
> did i miss
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
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
--- Comment #3 from H.J. Lu ---
Please try users/hjl/pr18028 branch at
https://github.com/hjl-tools/binutils-gdb
--
You are receiving this mail because:
You are on the CC list for the bug.
___
https://sourceware.org/bugzilla/show_bug.cgi?id=22831
H.J. Lu changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
--
You are
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
40 matches
Mail list logo