From: Cary Coutant <ccoutant@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: dwarf-discuss@lists.dwarfstd.org, gcc@gcc.gnu.org,
gdb@sourceware.org, Doug Evans <dje@google.com>,
Paul Pluzhnikov <ppluzhnikov@google.com>,
Sterling Augustine <saugustine@google.com>
Subject: Re: RFC: DWARF Extensions for Separate Debug Info Files ("Fission")
Date: Fri, 23 Sep 2011 17:50:00 -0000 [thread overview]
Message-ID: <CAHACq4q=KWQdh2ErgDMSMf-PKezdLD3kFcAkNdgYCMEADqncug@mail.gmail.com> (raw)
In-Reply-To: <20110923135109.GA22315@host1.jankratochvil.net>
>> * .debug_pubtypes - Public types for use in building the
>> .gdb_index section at link time. This section will have an
>> extended format to allow it to represent both types in the
>> .debug_dwo_info section and type units in .debug_types.
> ^^^^^^^^^^^^^^^
> = .dwo_info , maybe both .debug_info and .dwo_info
>
>
>> * .dwo_abbrev - Defines the abbreviation codes used by the
>> .debug_dwo_info section.
> ^^^^^^^^^^^^^^^
> = .dwo_info
Thanks, I've fixed the wiki page.
> I find this .dwo_* setup is great for rapid development rebuilds but it should
> remain optional as the currently used DWARF final separate .debug info file is
> smaller than all the .dwo files together. In the case of the final linked
> .debug builds (rpm/deb/...) one does not consider the build speed as important.
> It probably does not make sense to merge + convert .dwo files back to a single
> .debug file for the rpm/deb/... build performance reasons.
Yes, we'll definitely make this a compile-time option.
While I haven't finished designing the package format for collecting
all the .dwo files, I do plan on having the packaging tool do at least
duplicate type elimination to reduce the size of the package file.
-cary
next prev parent reply other threads:[~2011-09-23 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 0:22 Cary Coutant
2011-09-23 2:36 ` Jason Molenda
2011-09-23 2:26 ` Paul Pluzhnikov
2011-09-23 17:58 ` Cary Coutant
2011-09-23 21:02 ` Jason Molenda
2011-09-23 21:35 ` [Dwarf-Discuss] " John DelSignore
2011-09-23 13:51 ` Jan Kratochvil
2011-09-23 17:50 ` Cary Coutant [this message]
2011-10-20 21:43 ` 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='CAHACq4q=KWQdh2ErgDMSMf-PKezdLD3kFcAkNdgYCMEADqncug@mail.gmail.com' \
--to=ccoutant@google.com \
--cc=dje@google.com \
--cc=dwarf-discuss@lists.dwarfstd.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=ppluzhnikov@google.com \
--cc=saugustine@google.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).