From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24965] [dwz] Faster hashing using native insns
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-24965-11298-xClMtuDwQh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24965-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24965
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 11975
--> https://sourceware.org/bugzilla/attachment.cgi?id=11975&action=edit
Add --native-hash
This patch modifies crc32c-intel.patch to make the functionality
off-by-default, and available using a command line option --native-hash.
A first experiment with dwz-ing a cc1 binary, show ~10% speed improvement:
...
$ ../measure/experiment.sh
cmd: ./dwz -L100000000 -l100000000 cc1 -o cc1.dwz
1/10
2/10
3/10
4/10
5/10
6/10
7/10
8/10
9/10
10/10
cmd: ./dwz -L100000000 -l100000000 --native-hash cc1 -o cc1.dwz
1/10
2/10
3/10
4/10
5/10
6/10
7/10
8/10
9/10
10/10
real:
series: 9040 7073 7184 7060 7071 7149 6987 7120 7062 7095
mean: 7284.10 (100%)
stddev: 619.31
series: 6434 6442 6458 6580 6363 6374 6372 6369 6461 6422
mean: 6427.50 (88.24%)
stddev: 65.93
user:
series: 7320 6876 6886 6912 6902 6886 6830 6947 6916 6912
mean: 6938.70 (100%)
stddev: 137.46
series: 6265 6258 6269 6323 6214 6220 6208 6208 6237 6261
mean: 6246.30 (90.02%)
stddev: 36.30
sys:
series: 399 196 292 148 168 252 156 172 144 180
mean: 210.70 (100%)
stddev: 81.39
series: 168 184 188 252 148 152 164 160 220 160
mean: 179.60 (85.24%)
stddev: 33.12
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-09-04 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 [Bug default/24965] New: " vries at gcc dot gnu.org
2019-01-01 0:00 ` [Bug default/24965] " marxin.liska at gmail dot com
2019-01-01 0:00 ` jakub at redhat dot com
2019-01-01 0:00 ` jakub at redhat dot com
2019-01-01 0:00 ` vries at gcc dot gnu.org [this message]
2019-01-01 0:00 ` jakub at redhat dot com
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` marxin.liska at gmail dot com
2019-01-01 0:00 ` marxin.liska at gmail 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-24965-11298-xClMtuDwQh@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).