From: Tom de Vries <tdevries@suse.de>
To: Michael Matz <matz@suse.de>
Cc: dwz@sourceware.org, jakub@redhat.com
Subject: Re: [RFC 1/13][odr] Cover letter
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <f4dd4031-0698-e6eb-42fb-743e0eee2df7@suse.de> (raw)
In-Reply-To: <alpine.LSU.2.21.1912101736100.29201@wotan.suse.de>
On 10-12-2019 18:41, Michael Matz wrote:
> The additional reduction of using the ODR rule
> on cc1 isn't as big as I thought in the past, probably the largest stuff
> in .debug_info aren't type descriptions anymore, but still, it's a 22%
> reduction on top, so nothing to sneeze at. (Maybe for firefox it's more,
> I remember Honza moaning about many multiple struct type chains that
> only differed in the completeness of their pointer members)
FYI, I'm currently investigating a factor 3 execution time regression on
clang-10 (the largest I've tested sofar, at 111 million DIEs), and there
the difference between --no-odr and --odr --odr-mode=basic is larger.
--no-odr:
..
$ diff.sh clang-10-10.0.0-0.20190817snap5.fc30.x86_64.debug 1
.debug_info red: 30.55% 1769020251 1228593816
.debug_abbrev red: -2.54% 12122350 12430622
.debug_str red: 0% 135646131 135646131
total red: 28.18% 1916788732 1376670569
...
--odr --odr-mode=basic:
...
$ diff.sh clang-10-10.0.0-0.20190817snap5.fc30.x86_64.debug 1
.debug_info red: 66.90% 1769020251 585587333
.debug_abbrev red: 20.81% 12122350 9599834
.debug_str red: 0% 135646131 135646131
total red: 61.88% 1916788732 730833298
...
Thanks,
- Tom
prev parent reply other threads:[~2019-12-12 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Tom de Vries
2019-01-01 0:00 ` Michael Matz
2019-01-01 0:00 ` Tom de Vries
2019-01-01 0:00 ` Michael Matz
2019-01-01 0:00 ` Tom de Vries
2019-01-01 0:00 ` Michael Matz
2019-01-01 0:00 ` Tom de Vries [this message]
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=f4dd4031-0698-e6eb-42fb-743e0eee2df7@suse.de \
--to=tdevries@suse.de \
--cc=dwz@sourceware.org \
--cc=jakub@redhat.com \
--cc=matz@suse.de \
/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).