From: ASSI <Stromeko@nexgo.de>
To: binutils@sourceware.org
Subject: Re: GNU Binutils 2.41 release
Date: Fri, 04 Aug 2023 21:57:19 +0200 [thread overview]
Message-ID: <87350ytwbk.fsf@Rainer.invalid> (raw)
In-Reply-To: <87bkfta1mf.fsf@redhat.com> (Nick Clifton via Binutils's message of "Sun, 30 Jul 2023 15:57:12 +0100")
Nick Clifton via Binutils writes:
> We are pleased to announce that version 2.41 of the GNU Binutils project
> sources have been released and are now available for download at:
[…]
I see massive performance degradation in ld on Cygwin when linking
libraries or executables with a large number of objects.
For example compiling protobuf-21.12:
binutils-2.39: 1420.820u 143.747s 3:20.37 780.8% 0+0k 0+0io 41531073pf+0w
binutils-2.40: 1429.088u 140.548s 3:18.48 790.8% 0+0k 0+0io 41615637pf+0w
binutils-2.41: 1496.555u 524.457s 10:07.31 332.7% 0+0k 0+0io 41570112pf+0w
The linking step alone:
binutils-2.39: 14.212u 2.614s 0:20.54 81.8% 0+0k 0+0io 1909884pf+0w
binutils-2.40: 13.371u 0.839s 0:20.46 69.4% 0+0k 0+0io 1910885pf+0w
binutils-2.41: 85.507u 373.960s 7:55.39 96.6% 0+0k 0+0io 1905021pf+0w
I have another much larger application where the linking went from
seconds to over an hour.
The fact that a lot of that extra time is spent in system might provide
a clue for finding the culprit. BUt there's extra time in user as well
and it seems to scale superlinearly with the number of objects. It's
possible that objdump performance has also suffered, I've not yet
checked this in detail.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2023-08-04 19:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 14:57 Nick Clifton
2023-07-31 17:25 ` H.J. Lu
2023-08-01 9:43 ` Nick Clifton
2023-08-01 10:15 ` Tsukasa OI
2023-08-04 10:37 ` Nick Clifton
2023-08-04 18:02 ` H.J. Lu
2023-08-04 19:57 ` ASSI [this message]
2023-08-05 0:38 ` Sam James
2023-08-05 10:08 ` ASSI
2023-08-06 3:00 ` Tsukasa OI
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87350ytwbk.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).