From: Segher Boessenkool <segher@kernel.crashing.org>
To: Andrea Corallo <andrea.corallo@arm.com>
Cc: gcc-patches@gcc.gnu.org, nd@arm.com,
Richard Earnshaw <richard.earnshaw@arm.com>
Subject: Re: [PATCH 2/2] Aarch64: Add branch diluter pass
Date: Tue, 28 Jul 2020 17:07:03 -0500 [thread overview]
Message-ID: <20200728220703.GD17447@gate.crashing.org> (raw)
In-Reply-To: <87r1sv1nb5.fsf@arm.com>
Hi!
On Tue, Jul 28, 2020 at 07:55:58PM +0100, Andrea Corallo wrote:
> > [ Btw, the mailing list archive will not show your attachments (just lets
> > me download them); naming the files *.txt probably works, but you can
> > also use a sane mime type (like, text/plain) ].
>
> [ Sure can do it np, I'm just less sure if text/x-diff is such and
> insane mime type for a mailing list software :) ]
Well, first and foremost, it does not *work* with our current mailing
list setup. Also, anything x- only makes sense if you know the software
the receiver runs (and of course you don't, this is public email, with
hundreds or thousands of readers).
> > Can you share a geomean improvement as well? Also something like 0.4%
> > is sounds like, or is it more?
>
> After my first measure I was suggestted by a colleague a less noisy
> system to benchmark on and a more reproducable methodology. I repeated
> the tests on N1 with the following results:
>
> | Benchmark | Est. Peak Rate ration |
> | | diluted / baseline |
> |----------------+-----------------------|
> | 400.perlbench | 1.018x |
> | 401.bzip2 | 1.004x |
> | 403.gcc | 0.987x |
> | 429.mcf | 1.000x |
> | 445.gobmk | 0.998x |
> | 456.hmmer | 1.000x |
> | 458.sjeng | 1.008x |
> | 462.libquantum | 1.014x |
> | 464.h264ref | 1.004x |
> | 471.omnetpp | 1.017x |
> | 473.astar | 1.007x |
> | 483.xalancbmk | 0.998x |
Cool. Well, gcc has a pretty big drop, what's up with that? Everything
else looks just great :-)
> I was explained xalanc tend to be very noisy being memory bound so this
> explains the difference, not sure why sjeng looks less good.
Sjeng is very jumpy code, so of course your patch will influence it a
lot. No idea why it is less positive this run.
> The
> overall ratio comparing spec rates is +~0.44%.
Yup, a nice healthy improvement :-)
Segher
next prev parent reply other threads:[~2020-07-28 22:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 10:02 [PATCH 1/2] Add new RTX instruction class FILLER_INSN Andrea Corallo
2020-07-22 10:09 ` [PATCH 2/2] Aarch64: Add branch diluter pass Andrea Corallo
2020-07-22 10:39 ` Andrew Pinski
2020-07-22 13:53 ` Andrea Corallo
2020-07-22 16:43 ` Segher Boessenkool
2020-07-22 19:45 ` Andrea Corallo
2020-07-23 22:47 ` Segher Boessenkool
2020-07-24 7:01 ` Andrea Corallo
2020-07-24 11:53 ` Segher Boessenkool
2020-07-24 13:21 ` Andrea Corallo
2020-07-24 22:09 ` Segher Boessenkool
2020-07-28 18:55 ` Andrea Corallo
2020-07-28 22:07 ` Segher Boessenkool [this message]
2020-07-22 12:24 ` [PATCH 1/2] Add new RTX instruction class FILLER_INSN Richard Biener
2020-07-22 13:16 ` Richard Earnshaw (lists)
2020-07-22 14:51 ` Andrea Corallo
2020-07-22 18:41 ` Joseph Myers
2020-07-24 21:18 ` Segher Boessenkool
2020-07-26 18:19 ` Eric Botcazou
2020-07-28 19:29 ` Andrea Corallo
2020-08-19 9:13 ` Andrea Corallo
2020-08-19 10:52 ` Richard Sandiford
2020-08-19 17:28 ` Segher Boessenkool
2020-08-19 16:51 ` Segher Boessenkool
2020-08-19 17:47 ` Andrea Corallo
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=20200728220703.GD17447@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=andrea.corallo@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.com \
--cc=richard.earnshaw@arm.com \
/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).