From: Jerome Guitton <guitton@adacore.com>
To: gdb-patches@sources.redhat.com
Subject: [Bug symtab/8367] [RFA] performance improvement of lookup_partial_symtab
Date: Wed, 14 Jan 2009 17:46:00 -0000 [thread overview]
Message-ID: <20090114174542.GM84382@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
The move to bugzilla has "resurrected" this patch; I suggested it
several years ago, but it's still relevant.
The problem is explained in details in the comment (very useful when I
had to double-check that the patch was not obsolete, actually). To
summarize it: lookup_partial_symtab is particularly slow when it has
been given an absolute path. The reason is that it needs to build the
full filename for every psymtab; when building this full filename, the
corresponding file is opened/closed by find_and_open_source. As a
consequence, in the worst case, the loop ends up opening/closing
every source file of the application. Pretty bad for a big application,
in particular if the sources are located on a slow file system.
The idea of the patch is to avoid building the psymtab full filename
if the basenames are different.
Tested on linux, no regression.
OK to apply?
2009-01-14 Jerome Guitton <guitton@adacore.com>
* symtab.c (lookup_partial_symtab): When looking up an absolute path
in the partial symtabs, compare the base names before checking the
full names.
[-- Attachment #2: lookup_partial_symtab.dif --]
[-- Type: video/dv, Size: 2457 bytes --]
next reply other threads:[~2009-01-14 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 17:46 Jerome Guitton [this message]
2009-01-15 9:45 ` Jerome Guitton
2009-04-28 19:57 ` Joel Brobecker
2009-04-29 8:54 ` Jerome Guitton
2009-04-28 20:00 ` Joel Brobecker
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=20090114174542.GM84382@adacore.com \
--to=guitton@adacore.com \
--cc=gdb-patches@sources.redhat.com \
/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