From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [0/12] RFC: support for 'dwz -m'
Date: Wed, 13 Jun 2012 19:37:00 -0000 [thread overview]
Message-ID: <878vfrxaur.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87y5o1lhrt.fsf@fleche.redhat.com> (Tom Tromey's message of "Tue, 05 Jun 2012 12:45:26 -0600")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> I'm posting this series as an RFC. I intend to check it in, just not
Tom> yet -- it is too large, IMO, to go in just before 7.5, and also we're
Tom> hoping to get some official DWARF constants assigned beforehand (see
Tom> patch #1). Finally, this series needs a couple of links to
Tom> documentation, which I think isn't ready yet.
I'm going to post a new version of this series.
I dropped patch #1, because Jakub put the equivalent patch into gcc and
src already. It has a link to the DWARF proposal:
http://www.dwarfstd.org/ShowIssue.php?issue=120604.1&type=open
Of course, because of this, the patch numbers all change, leading to
general confusion. I plan to handle this by sending follow-ups to the
most recent version of the patches.
Also, I'm only planning to repost the patches that have changed -- just
the last 3.
Tom> I've regression tested the series using plain 'dwz -m', but not
Tom> multifile compression in conjunction with .gdb_index (the dwz change
Tom> here isn't ready yet). I will do this testing before committing.
I did this and there are no regressions as compared to a test suite run
using just .gdb_index. (.gdb_index has a regression against a plain
test run.)
Tom
prev parent reply other threads:[~2012-06-13 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 18:45 Tom Tromey
2012-06-05 18:56 ` Tom Tromey
2012-06-13 19:37 ` Tom Tromey [this message]
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=878vfrxaur.fsf@fleche.redhat.com \
--to=tromey@redhat.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