From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Michael Eager <eager@eagerm.com>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: SEGV in dwarf2read.c -- gdb-7.2
Date: Thu, 03 Nov 2011 16:43:00 -0000 [thread overview]
Message-ID: <m3ty6lrwbb.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20111103162026.GA12269@host1.jankratochvil.net> (Jan Kratochvil's message of "Thu, 3 Nov 2011 17:20:26 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> I guess for performance reasons, the CU header read-in
Jan> vs. load_full_comp_unit is a big difference. There are already
Jan> some PRs (such as 12828 (a)) where GDB needlessly expands too many
Jan> CUs "locking itself" by inacceptable performance.
Does the CU cache serve a useful purpose these days?
I wonder whether we could just remove it.
Tom
next prev parent reply other threads:[~2011-11-03 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 16:12 Michael Eager
2011-11-03 16:20 ` Jan Kratochvil
2011-11-03 16:43 ` Tom Tromey [this message]
2011-11-03 16:55 ` Jan Kratochvil
2011-11-03 17:13 ` Michael Eager
2011-11-03 17:22 ` Jan Kratochvil
2011-11-03 17:37 ` Michael Eager
2011-11-03 17:05 ` Michael Eager
2011-11-03 17:25 ` Jan Kratochvil
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=m3ty6lrwbb.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eager@eagerm.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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