From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24388] Disabling DIE deduplication improves compression for hello
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-24388-11298-weutCWbHHU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24388-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24388
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
I tried the same with dwz as dwz input:
...
$ dwz dwz-for-test -o dwz-for-test.dwz
$ diff.sh dwz-for-test dwz-for-test.dwz
.debug_info red: 15% 119827 102801
.debug_abbrev red: 2% 4009 3964
.debug_str red: 0% 20731 20731
total red: 12% 144567 127496
$ dwz dwz-for-test -o dwz-for-test.dwz.2
$ diff.sh dwz-for-test dwz-for-test.dwz.2
.debug_info red: 14% 119827 103872
.debug_abbrev red: 23% 4009 3094
.debug_str red: 0% 20731 20731
total red: 12% 144567 127697
...
This seems to be a point where using DIE deduplication is just better than not
using it.
So, with this being the DIE counts:
...
$ count-dies.sh hello
130
$ count-dies.sh dwz-for-test
10.393
$ count-dies.sh cc1
10.188.941
...
perhaps a cut-off point of 100.000 would do.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-03-26 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 [Bug default/24388] New: " vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org [this message]
2020-01-01 0:00 ` [Bug default/24388] " vries at gcc dot gnu.org
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-24388-11298-weutCWbHHU@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).