From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: [0/12] RFC: support for 'dwz -m'
Date: Tue, 05 Jun 2012 18:45:00 -0000 [thread overview]
Message-ID: <87y5o1lhrt.fsf@fleche.redhat.com> (raw)
I'm posting this series as an RFC. I intend to check it in, just not
yet -- it is too large, IMO, to go in just before 7.5, and also we're
hoping to get some official DWARF constants assigned beforehand (see
patch #1). Finally, this series needs a couple of links to
documentation, which I think isn't ready yet.
Jakub recently posted about his new DWARF compression tool, 'dwz':
http://gcc.gnu.org/ml/gcc/2012-04/msg00686.html
The 'multifile' branch of the dwz repository implements support for a
multi-file mode. The idea behind this mode is that commonalities
between a set of files are extracted into a new '.dwz' file, that is
then referenced by the rewritten original files.
We intend to use this when creating debuginfo RPMs. It yields a nice
compression boost for some packages.
This patch series implements support for the needed DWARF extensions in
gdb. Part of the series comes from my earlier minsym sharing series.
Some of these are really just plain cleanups that I probably should have
put in long ago.
The bulk of the real work is in patches #9 and #10.
I'd like to thank Doug for his Fission work, which made this much
simpler than it otherwise would have been.
I've regression tested the series using plain 'dwz -m', but not
multifile compression in conjunction with .gdb_index (the dwz change
here isn't ready yet). I will do this testing before committing.
Tom
next reply other threads:[~2012-06-05 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 18:45 Tom Tromey [this message]
2012-06-05 18:56 ` Tom Tromey
2012-06-13 19:37 ` 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=87y5o1lhrt.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