public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
Cc: Mark Wielaard <>
Subject: [PATCH] PR27402 Document DWARF5 support
Date: Fri, 12 Feb 2021 14:14:48 +0100	[thread overview]
Message-ID: <> (raw)

	* dwz.1: Explain what subset of DWARF5 is supported, update date,
	authors and add a reference to the dwz home page and mailinglist.
 dwz.1 | 35 ++++++++++++++++++++++++++++++-----
 1 file changed, 30 insertions(+), 5 deletions(-)

diff --git a/dwz.1 b/dwz.1
index 709506c..23ed8c1 100644
--- a/dwz.1
+++ b/dwz.1
@@ -1,4 +1,4 @@
-.TH dwz 1 "15 June 2012"
+.TH dwz 1 "15 Feb 2021"
 dwz \- DWARF optimization and duplicate removal tool
@@ -15,9 +15,26 @@ compilation units (CUs) for duplicated information and using
 to import it into each CU that needs it.
-The tool handles DWARF 32-bit format debugging sections of versions
-2, 3 and 4 and GNU extensions on top of those, though using DWARF 4
-or worst case DWARF 3 is strongly recommended.
+The tool handles DWARF 32-bit format debugging sections of versions 2,
+3, 4, most of version 5 and GNU extensions on top of those.  It is
+strongly recommended to use at least DWARF 3, but using DWARF 4 or
+higher will work much better.
+While most of DWARF 5 is supported dwz doesn't yet generate spec
+compliant DWARF Supplementary Object Files (DWARF 5, section
+7.3.6). Instead of a \fI.debug_sup\fR section it will generate a
+\fI.gnu_debugaltlink\fR section. And it will use the
+\fIDW_FORM_GNU_strp_alt\fR and \fIDW_FORM_GNU_reg_alt\fR, instead of
+\fIDW_FORM_strp_sup\fR and \fIDW_FORM_ref_sup\fR to keep compatibility
+with existing DWARF consumers.
+DWARF 4 \fI.debug_types\fR are supported, but DWARF 5 \fIDW_UT_type\fR
+units are not. Likewise \fI.gdb_index\fR is supported, but the DWARF 5
+\fI.debug_names\fR is not. Also some forms and sections that are only
+emitted by GCC when generating Split DWARF, \fIDW_FORM_strx\fR and
+\fI.debug_str_offsets\fR, \fIDW_FORM_addrx\fR and \fI.debug_addr\fR,
+\fIDW_FORM_rnglistx\fR and \fIDW_FORM_loclistsx\fR, are not supported
 The tool has two main modes of operation, without the
 \fI-m\fR option it attempts to optimize DWARF debugging information in each
@@ -155,6 +172,14 @@ is equivalent to \fIdwz a.out\fR command.
 .BR gdb (1).
-Jakub Jelinek <>.
+Jakub Jelinek <>,
+Tom de Vries <>,
+Mark Wielaard <>
+Use the Bugzilla link of the project web page or our mailing list.
+.BR ", " <> .

             reply	other threads:[~2021-02-12 13:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 13:14 Mark Wielaard [this message]
2021-02-18 13:50 ` Mark Wielaard

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).