public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: binutils@sourceware.org
Subject: [PATCH 0/8] ld: Speed up section selection
Date: Fri, 25 Nov 2022 16:44:23 +0000 (UTC)	[thread overview]
Message-ID: <alpine.LSU.2.20.2211251605210.24878@wotan.suse.de> (raw)

Hello,

so this series rewrites how ld selects sections, i.e. how the globs inside 
linker scripts are evaluated.  My speed testcase is always linking cc1, 
a reasonably sized c++ program with many input files and sections (due to 
templates and section groups).  I will use x86-64.  The characteristics of 
that testcase are:

* 674 input files
* 300050 input sections
* 129 wild statements in the linker script
* 179 section selecttors in these wild statements (not all of them globs)

With an -O2 build ld.bfd we start with this before the series:

overall link time:
           4.2823 +- 0.0188 seconds time elapsed  ( +-  0.44% )

relevant pieces of the profile (overall this has 16900 samples):
     percentage    Samples program shared object symbol name
     5.82%           937  ld-new   ld-new        walk_wild_section_specs3_wild2
     4.45%           718  ld-new   ld-new        walk_wild_section_specs1_wild1
     2.97%           480  ld-new   ld-new        walk_wild_section_specs2_wild1
     1.97%           317  ld-new   ld-new        walk_wild_section_general
     0.85%           137  ld-new   ld-new        match_simple_wild

After the series this will be:

overall link time:
           3.62733 +- 0.00779 seconds time elapsed  ( +-  0.21% )

relevant pieces of the profile (overall this has 14244 samples):
     percentage    Samples program shared object symbol name
     0.67%            97  ld-new   ld-new        resolve_wild_sections.part.0
 
Yep, that's it, 97 samples remain from the initial 2500 samples for the 
whole of section selection.  I have further patches that speedup GNU ld, 
but this series is only about the section selection process, which is the 
second top-most profile entry and the only code taking considerable time 
that isn't in libbfd.

The way the series works is to first reshuffle the order of the overall 
loop structure matching all sections against all wild statements.  Then we 
can memoize these results (which needs some adjustments), then we can use 
a prefix tree to quickly rule out possible matches, and then we cleaup.

For review purpose I decided to not merge together some of the patches in 
the series.  In particular it adds some interface into libbfd (in 2/8) 
that gets removed again later (in 7/8).  Also the patches adding 
functionality often only comment out the old variants that are then only 
removed in a later patch.  I think in this case that makes it easier to 
review (I looked at the overall squashed patch and it's quite confusing).

I will also have a question in 4/8 whose answer might make the bfd change 
useful, so that it wouldn't have to be removed.

I've tested the whole series without regression on all of Alans targets 
(158 of them).  So, okay for master? :)


Ciao,
Michael.


Michael Matz (8):
  section-select: Lazily resolve section matches
  section-select: Deal with sections added late
  section-select: Implement a prefix-tree
  section-select: Completely rebuild matches
  section-select: Remove unused code
  section-select: Cleanup
  section-select: Remove bfd_max_section_id again
  section-select: Fix exclude-file-3

 ld/ldlang.c                                | 672 +++++++++------------
 ld/ldlang.h                                |  13 +-
 ld/testsuite/ld-scripts/exclude-file-3.map |   4 +-
 3 files changed, 295 insertions(+), 394 deletions(-)

-- 
2.36.1

             reply	other threads:[~2022-11-25 16:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 16:44 Michael Matz [this message]
2022-11-30  7:28 ` Alan Modra
2022-11-30 16:18   ` Michael Matz

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=alpine.LSU.2.20.2211251605210.24878@wotan.suse.de \
    --to=matz@suse.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).