From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [3/4] RFC: add DWARF index support
Date: Tue, 06 Jul 2010 17:37:00 -0000 [thread overview]
Message-ID: <20100706173734.GB25792@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3y6docy4d.fsf@fleche.redhat.com>
On Tue, 06 Jul 2010 19:34:58 +0200, Tom Tromey wrote:
> I am not sure about the CRC thing. That would result in a needless
> slowdown. It might be faster to just read psymtabs after all.
My mistake, yes, I agree.
Regards,
Jan
next prev parent reply other threads:[~2010-07-06 17:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 22:46 Tom Tromey
2010-07-04 18:18 ` Jan Kratochvil
2010-07-04 19:28 ` Jan Kratochvil
2010-07-06 16:50 ` Tom Tromey
2010-07-06 17:11 ` Jan Kratochvil
2010-07-06 17:31 ` Tom Tromey
2010-07-06 17:36 ` Jan Kratochvil
2010-07-06 17:35 ` Tom Tromey
2010-07-06 17:37 ` Jan Kratochvil [this message]
2010-07-08 17:01 ` Tom Tromey
2010-07-08 18:25 ` Eli Zaretskii
2010-07-08 20:35 ` Tom Tromey
2010-07-08 20:52 ` Eli Zaretskii
2010-07-08 17:02 ` 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=20100706173734.GB25792@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--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