From: Alejandro Martinez Vicente <Alejandro.MartinezVicente@arm.com>
To: a b <blue_3too@hotmail.com>, gcc gcc <gcc@gcc.gnu.org>
Cc: nd <nd@arm.com>
Subject: RE: What are the optimizations that contribute to ~70% improvement on SPEC06 hmmer benchmark?
Date: Fri, 24 May 2019 08:23:00 -0000 [thread overview]
Message-ID: <DB7PR08MB316334B6DC746E4EF0D28217E5020@DB7PR08MB3163.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <DM6PR18MB30330A7DA7E31B7C2BE3DEB2C9010@DM6PR18MB3033.namprd18.prod.outlook.com>
> -----Original Message-----
> From: gcc-owner@gcc.gnu.org <gcc-owner@gcc.gnu.org> On Behalf Of a b
> Sent: 23 May 2019 21:04
> To: gcc gcc <gcc@gcc.gnu.org>
> Subject: What are the optimizations that contribute to ~70% improvement on
> SPEC06 hmmer benchmark?
>
> Recently I happen to notice that there is more than 70% performance
> improvement for SPEC06 hmmer benchmark from Linaro GCC 5.2-2015.11-
> 2<https://releases.linaro.org/components/toolchain/binaries/5.2-2015.11-2/>
> to GCC 10.0 on ARM platforms.
>
> I did some quick searching and think loop
> distribution<https://community.arm.com/developer/tools-
> software/tools/b/tools-software-ides-blog/posts/gnu-toolchain-performance-
> in-2018> and
> vectorization<http://www.teratec.eu/library/pdf/forum/2018/Presentations/04
> _Eric_Van_Hensbergen_Arm_Forum_Teratec_2018.pdf> contribute 25% and
> 30%, respectively. But they still don't add up to 70%. Can you explain what else
> is helping here?
1.25 x 1.3 = 1.625 Not far from 1.7 😊
Alejandro
>
> Thanks
prev parent reply other threads:[~2019-05-24 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 20:04 a b
2019-05-24 8:23 ` Alejandro Martinez Vicente [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=DB7PR08MB316334B6DC746E4EF0D28217E5020@DB7PR08MB3163.eurprd08.prod.outlook.com \
--to=alejandro.martinezvicente@arm.com \
--cc=blue_3too@hotmail.com \
--cc=gcc@gcc.gnu.org \
--cc=nd@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).