public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/17604] New: Stop demangling ELF symbols, at least by default when we have DWARF
Date: Fri, 14 Nov 2014 23:59:00 -0000	[thread overview]
Message-ID: <bug-17604-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=17604

            Bug ID: 17604
           Summary: Stop demangling ELF symbols, at least by default when
                    we have DWARF
           Product: gdb
           Version: 7.8
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

PR 17603 made me want to try an experiment of measuring gdb startup time on my
monster benchmark if we stop demangling ELF symbols.

I did a quick experiment, but the data is promising.

In the past I've measured 12 seconds of the 13 seconds of gdb startup time
being due to reading ELF symbols (measured by just #if 0-ing out the code to
read them).

If I #if 0 out the code to generate and store demangled copies of ELF symbols
then the 13 seconds goes down to 2.5 seconds.

Nice.

So maybe we can generate demangled copies of ELF symbols lazily.

One question I'd like to see answered is under what conditions do we *need*
demangled ELF symbols *when* we have DWARF.

Having demangled copies of ELF symbols can hide bugs in reading DWARF.
E.g., PR 17602.

I'm filing this separately from 17603 as this PR addresses the performance of
reading ELF symbols.  PR 17603 addresses the related issue where usage of
minsyms hides bugs in the DWARF reader.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2014-11-14 23:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14 23:59 dje at google dot com [this message]
2014-11-15  0:02 ` [Bug symtab/17604] " dje at google dot com
2014-11-15  0:10 ` dje at google dot com
2014-11-18 15:17 ` gbenson at redhat dot com
2014-11-19 19:48 ` dje at google dot com
2015-06-19 16:50 ` dje at google dot com

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=bug-17604-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).