From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/25141] New: Doing dwz single-file optimization before dwz multifile optimization reduces effectiveness
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-25141-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25141
Bug ID: 25141
Summary: Doing dwz single-file optimization before dwz
multifile optimization reduces effectiveness
Product: dwz
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: vries at gcc dot gnu.org
CC: dwz at sourceware dot org
Target Milestone: ---
When doing the self-multi-file optimization on a hello world executable, we
manage a total reduction of 78%:
...
$ cp hello 1; cp 1 2; ./dwz -m 3 1 2
$ ../measure/diff.sh hello 1
.debug_info red: 66.19% 1467 496
.debug_abbrev red: 50.65% 624 308
.debug_str red: 100.00% 1595 0
total red: 78.19% 3686 804
...
However, if we first do the single-file mode optimization step using a separate
invocation, we achieve a total reduction of only 54%:
...
$ cp hello 4; ./dwz 4; cp 4 5; ./dwz -m 6 4 5
./dwz: 4: DWARF compression not beneficial - old size 3400 new size 3400
./dwz: 5: DWARF compression not beneficial - old size 3400 new size 3400
$ ../measure/diff.sh hello 4
.debug_info red: 24.20% 1467 1112
.debug_abbrev red: 8.82% 624 569
.debug_str red: 100.00% 1595 0
total red: 54.40% 3686 1681
...
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2019-10-28 14:01 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=bug-25141-11298@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@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).