Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/commit/dwarf] Create partial symbols for nested 	subprograms
Date: Thu, 11 Sep 2008 18:38:00 -0000	[thread overview]
Message-ID: <20080911183730.GA17809@caradoc.them.org> (raw)
In-Reply-To: <20080911175422.GS12222@adacore.com>

On Thu, Sep 11, 2008 at 10:54:22AM -0700, Joel Brobecker wrote:
> > Do you have any performance data for GDB startup with this change?
> 
> I am not sure I am doing the right kind of performance test, so if you
> have some better suggestions, please let me know. For now, here is what
> I did:
> 
>   . I used one of the large Ada applications we have:
>     It is 290MB in size - reduced to 160MB when I strip the debugging
>     info => the debugging info size is roughly 130MB.
>     The number of real lines of code is 700K spread in ~3500 files,
>     and it has a total of 39,000 subprograms declared in the debugging
>     info.
> 
>   . To measure the startup time, I used the --statistics command-line
>     switch.

I usually use 'gdb -batch foo.exe' to time reading partial symbols,
and 'gdb -readnow -batch foo.exe' to time full symbols (only partial
symbols are at issue here).

> It looks like roughly a 4% increase in startup time. Not sure whether
> that's considered a large increase or not - I just think that it's not
> noticeable. None of our users have reported issues with startup time.

Your users must be more patient than mine or Tom's :-)  I consider
startup time to be pretty important, and I've been working on bringing
it down... Tom's been working on an even more drastic version.

> But, to make sure that only languages that have this feature get hit,
> I adjusted the patch to only search nested procedure when the language
> allows them.

Does it work / help to do the check here too:

>  	  && (load_all
>  	      || last_die->tag == DW_TAG_namespace
>  	      || last_die->tag == DW_TAG_enumeration_type
> +	      || last_die->tag == DW_TAG_subprogram
> +	      || last_die->tag == DW_TAG_lexical_block
>  	      || (cu->language != language_c
>  		  && (last_die->tag == DW_TAG_class_type
>  		      || last_die->tag == DW_TAG_interface_type

That'll bring the memory usage back down for non-Ada.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-09-11 18:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 20:20 Joel Brobecker
2008-09-10 20:35 ` Daniel Jacobowitz
2008-09-10 21:38   ` Tom Tromey
2008-09-11  5:01     ` Joel Brobecker
2008-09-11 22:15       ` Tom Tromey
2008-09-11 22:28         ` Daniel Jacobowitz
2008-09-11 22:33           ` Tom Tromey
2008-09-12  4:19           ` Joel Brobecker
2008-09-11 17:55   ` Joel Brobecker
2008-09-11 18:38     ` Daniel Jacobowitz [this message]
2008-09-11 21:53       ` Joel Brobecker
2008-09-13 15:14         ` Daniel Jacobowitz
2008-09-13 22:21           ` Joel Brobecker
2008-09-11 22:44       ` Tom Tromey
2008-09-12  4:18         ` Joel Brobecker
2008-09-12 16:51           ` Tom Tromey
2008-09-12 16:56             ` Joel Brobecker
2008-09-12 17:19               ` Tom Tromey
2008-09-12 17:43                 ` Joel Brobecker
2008-09-12 18:08                   ` Tom Tromey
2008-09-12 18:43                   ` Frank Ch. Eigler
2008-09-12 20:31                     ` Tom Tromey

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=20080911183730.GA17809@caradoc.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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