public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
	archer@sourceware.org,  Jakub Jelinek <jakub@redhat.com>
Subject: Re: Inter-CU DWARF size optimizations and gcc -flto
Date: Sun, 26 Feb 2012 15:09:00 -0000	[thread overview]
Message-ID: <CAN9gPaEvcr5jnA5PTNHgBpNa120JDp3JTUEYqN3kUkbbS0b=sg@mail.gmail.com> (raw)
In-Reply-To: <87hayio7ld.fsf@fleche.redhat.com>

On Wed, Feb 22, 2012 at 4:56 PM, Tom Tromey <tromey@redhat.com> wrote:
> Jan> (b) .gdb_index will have limited scope, only to select which
> Jan> objfiles to expand, no longer to select which CUs to expand.
>
> I suspect we are going to need a better approach here anyway.
> I sometimes hear about programs with more than 800 shared libraries.
> If you assume separate debuginfo this means 1600 objfiles.
> I think this will just crush most of the existing algorithms in gdb.

You are correct, it does crush GDB :-)  I routinely try - emphasis on
try - to use GDB on programs with between 2500 and 5500 shared
libraries.  It's agonizing.  I have another project I want to work on
first, and not much time for GDB lately, but this is absolutely on my
list to improve.

-- 
Thanks,
Daniel

  reply	other threads:[~2012-02-26 15:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 13:23 Jan Kratochvil
2012-02-01 13:32 ` Jakub Jelinek
2012-02-22 21:56 ` Tom Tromey
2012-02-26 15:09   ` Daniel Jacobowitz [this message]
2012-03-03  2:54     ` Tom Tromey
2012-03-05  0:25       ` Daniel Jacobowitz
2012-03-05 22:03         ` Tom Tromey
2012-03-15 12:51         ` Gary Benson

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='CAN9gPaEvcr5jnA5PTNHgBpNa120JDp3JTUEYqN3kUkbbS0b=sg@mail.gmail.com' \
    --to=drow@false.org \
    --cc=archer@sourceware.org \
    --cc=jakub@redhat.com \
    --cc=jan.kratochvil@redhat.com \
    --cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).