From: Mark Wielaard <mark@klomp.org>
To: dwz@sourceware.org
Cc: dwarf-discuss@lists.dwarfstd.org, gcc@gcc.gnu.org, gdb@sourceware.org
Subject: DWZ 0.17 released
Date: Sat, 11 Jul 2026 22:18:28 +0200 [thread overview]
Message-ID: <20260711201828.GF31804@gnu.wildebeest.org> (raw)
DWZ 0.17 has been released.
dwz - DWARF optimization and duplicate removal tool
dwz is a program that attempts to optimize DWARF debugging
information contained in ELF shared libraries and ELF executables
for size, by replacing DWARF information representation with
equivalent smaller representation where possible and by reducing
the amount of duplication using techniques from DWARF standard
appendix E - creating DW_TAG_partial_unit compilation units (CUs)
for duplicated information and using DW_TAG_imported_unit to
import it into each CU that needs it.
You can download dwz from the sourceware FTP server here:
https://sourceware.org/ftp/dwz/releases/
ftp://sourceware.org/pub/dwz/releases/
The vital stats:
Size md5sum Name
189KiB 3feead232f4862af3fb3e041c00ecfd6 dwz-0.17.tar.gz
152KiB fd653f7ca80a7222d4b7cc3497870e38 dwz-0.17.tar.xz
The tar files are signed (as dwz-0.17.tar.{gz,xz}.asc) with
https://www.klomp.org/mark/gnupg-pub.txt
There is a web page for DWZ at:
https://sourceware.org/dwz/
DWZ 0.17 now accepts (ELF or GNU) compressed debug sections on input.
== git shortlog ==
Daan De Meyer (1):
dwz: Accept compressed debug sections on input
Mark Wielaard (9):
lldb doesn't have a mailinglist anymore
Sync dwarf2.{def,h} and dwarfnames.c from gcc/libiberty
htab.c: Remove old-style function definitions
dwz.c (optimize_multifile): Init shstrtab and shstrtab_len after setjmp.
dwz: Print the max die limit when not optimizing in error messages
dwz: Fix stray comma in error format
Define ELFCOMPRESS_ZSTD if elf.h and libelf.h don't define it
Update FSF Copyright years to include 2025.
Bump version to 0.17
reply other threads:[~2026-07-11 20:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260711201828.GF31804@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=dwarf-discuss@lists.dwarfstd.org \
--cc=dwz@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@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