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/12707] physname regression: set print demangle off
Date: Sat, 15 Nov 2014 00:07:00 -0000	[thread overview]
Message-ID: <bug-12707-4717-RNIBlGlIFa@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12707-4717@http.sourceware.org/bugzilla/>

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

--- Comment #8 from dje at google dot com ---
Data point, from PR 17604.
In my monster benchmark, 12 of 13 seconds of gdb startup time (the time to get
to the prompt) is due to reading ELF symbols.
If I comment out the generation and storage of demangled copies of ELF symbols,
then startup time reduces to 2.5 seconds.
This is enough to make me seriously want to implement something along these
lines.

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


  parent reply	other threads:[~2014-11-15  0:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 14:58 [Bug symtab/12707] New: " jan.kratochvil at redhat dot com
2013-01-14 14:31 ` [Bug symtab/12707] " tromey at redhat dot com
2013-01-18 14:28 ` tromey at redhat dot com
2013-02-01 21:35 ` tromey at redhat dot com
2013-02-08 13:35 ` tromey at redhat dot com
2013-07-30  0:10 ` b.r.longbons at gmail dot com
2013-10-19 18:38 ` jan.kratochvil at redhat dot com
2013-10-19 19:40 ` dje at google dot com
2013-11-21 19:03 ` tromey at redhat dot com
2014-06-13 19:34 ` tromey at redhat dot com
2014-10-10 11:09 ` hgmnxact at gmail dot com
2014-11-15  0:07 ` dje at google dot com [this message]
2020-03-25 19:24 ` tromey at sourceware dot org
2020-04-24 21:36 ` cvs-commit at gcc dot gnu.org
2020-04-24 21:39 ` tromey at sourceware dot org

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-12707-4717-RNIBlGlIFa@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).