public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/20369] Support DW_TAG_type_unit
Date: Fri, 01 Jan 2016 00:00:00 -0000	[thread overview]
Message-ID: <bug-20369-9487-DR3v4a4KYO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20369-9487@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=20369

Ben Woodard <woodard at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |woodard at redhat dot com

--- Comment #16 from Ben Woodard <woodard at redhat dot com> ---
I just wanted to add a comment that --compress-debug-sections and DWZ are quite
different in their approaches. --compress-debug-sections simply uses zlib to
compress the DWARF while dwz actually replaces duplicated DWARF information
coming from different compilation units with references to each other. This is
particularly effective when applied to templated C++ code.

In theory once dwz has been applied the DWARF could even be compressed further
with zlib but I've never heard of anyone attempting this and I would be
surprised if it worked.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2016-07-21  8:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-01  0:00 [Bug default/20369] New: Assertion `m' failed in abidw: abg-dwarf-reader.cc:7472 andrew.c.morrow at gmail dot com
2016-01-01  0:00 ` [Bug default/20369] " andrew.c.morrow at gmail dot com
2016-01-01  0:00 ` [Bug default/20369] Support DW_TAG_type_unit dodji at redhat dot com
2016-01-01  0:00 ` [Bug default/20369] Assertion `m' failed in abidw: abg-dwarf-reader.cc:7472 andrew.c.morrow at gmail dot com
2016-01-01  0:00 ` [Bug default/20369] Support DW_TAG_type_unit andrew.c.morrow at gmail dot com
2016-01-01  0:00 ` [Bug default/20369] Assertion `m' failed in abidw: abg-dwarf-reader.cc:7472 mjw at redhat dot com
2016-01-01  0:00   ` Dodji Seketeli
2016-01-01  0:00 ` andrew.c.morrow at gmail dot com
2016-01-01  0:00 ` andrew.c.morrow at gmail dot com
2016-01-01  0:00 ` [Bug default/20369] Support DW_TAG_type_unit andrew.c.morrow at gmail dot com
2016-01-01  0:00 ` [Bug default/20369] Assertion `m' failed in abidw: abg-dwarf-reader.cc:7472 dodji at redhat dot com
2016-01-01  0:00 ` [Bug default/20369] Support DW_TAG_type_unit mjw at redhat dot com
2016-01-01  0:00 ` [Bug default/20369] Assertion `m' failed in abidw: abg-dwarf-reader.cc:7472 andrew.c.morrow at gmail dot com
2016-01-01  0:00 ` woodard at redhat dot com [this message]
2016-01-01  0:00 ` [Bug default/20369] Support DW_TAG_type_unit dodji at redhat dot com
2016-01-01  0:00 ` [Bug default/20369] Assertion `m' failed in abidw: abg-dwarf-reader.cc:7472 mjw at redhat dot com
2016-01-01  0:00 ` [Bug default/20369] Support DW_TAG_type_unit dodji at redhat dot com
2016-01-01  0:00 ` dodji at redhat dot com
2016-01-01  0:00 ` mjw at redhat dot com
2016-01-01  0:00 ` [Bug default/20369] Assertion `m' failed in abidw: abg-dwarf-reader.cc:7472 andrew.c.morrow at gmail dot com
2016-01-01  0:00 ` [Bug default/20369] Support DW_TAG_type_unit andrew.c.morrow at gmail dot com
2016-01-01  0:00 ` [Bug default/20369] Assertion `m' failed in abidw: abg-dwarf-reader.cc:7472 dodji at seketeli dot org
2016-01-01  0:00 ` [Bug default/20369] Support DW_TAG_type_unit andrew.c.morrow at gmail dot com
2016-01-01  0:00 ` dodji at redhat dot com
2016-01-01  0:00 ` [Bug default/20369] Assertion `m' failed in abidw: abg-dwarf-reader.cc:7472 andrew.c.morrow at gmail dot com
2016-01-01  0:00 ` dodji at redhat dot com

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=bug-20369-9487-DR3v4a4KYO@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libabigail@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).