public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rvmallad at amazon dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107413] Perf loss ~14% on 519.lbm_r SPEC cpu2017 benchmark with r8-7132-gb5b33e113434be
Date: Wed, 30 Nov 2022 04:15:19 +0000 [thread overview]
Message-ID: <bug-107413-4-sOSGAYDL9U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107413-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107413
--- Comment #16 from Rama Malladi <rvmallad at amazon dot com> ---
(In reply to Wilco from comment #15)
> (In reply to Rama Malladi from comment #14)
> > This fix also improved performance of 538.imagick_r by 15%. Did you have a
> > similar observation? Thank you.
>
> No, but I was using -mcpu=neoverse-n1 as my baseline. It's possible
> -mcpu=neoverse-v1 shows larger speedups, what gain do you get on the overall
> FP score?
I was using -mcpu=native and run on a Neoverse V1 arch (Graviton3). Here are
the scores I got (relative gains of latest mainline vs. an earlier mainline).
Latest mainline: 0976b012d89e3d819d83cdaf0dab05925b3eb3a0
Earlier mainline: f896c13489d22b30d01257bc8316ab97b3359d1c
fp 1-copy rate Ratio
503.bwaves_r 0.98
507.cactuBSSN_r 1.00
508.namd_r 0.97
510.parest_r NA
511.povray_r NA
519.lbm_r 1.16
521.wrf_r 1.00
526.blender_r 0.99
527.cam4_r NA
538.imagick_r 1.17
544.nab_r 1.01
549.fotonik3d_r NA
554.roms_r 1.00
geomean 1.03
next prev parent reply other threads:[~2022-11-30 4:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 9:16 [Bug tree-optimization/107413] New: Perf loss ~14% on 519.lbm_r SPEC cpu2017 benchmark rvmallad at amazon dot com
2022-10-26 9:20 ` [Bug tree-optimization/107413] " rvmallad at amazon dot com
2022-10-26 11:47 ` wilco at gcc dot gnu.org
2022-10-26 19:03 ` rvmallad at amazon dot com
2022-10-27 12:19 ` mark at gcc dot gnu.org
2022-10-28 10:41 ` rvmallad at amazon dot com
2022-10-28 10:46 ` rvmallad at amazon dot com
2022-11-01 12:48 ` [Bug tree-optimization/107413] Perf loss ~14% on 519.lbm_r SPEC cpu2017 benchmark with r8-7132-gb5b33e113434be wilco at gcc dot gnu.org
2022-11-02 0:29 ` rvmallad at amazon dot com
2022-11-02 23:39 ` rvmallad at amazon dot com
2022-11-04 17:26 ` wilco at gcc dot gnu.org
2022-11-07 7:42 ` rvmallad at amazon dot com
2022-11-24 13:30 ` cvs-commit at gcc dot gnu.org
2022-11-28 8:33 ` rvmallad at amazon dot com
2022-11-29 9:04 ` rvmallad at amazon dot com
2022-11-29 12:55 ` wilco at gcc dot gnu.org
2022-11-30 4:15 ` rvmallad at amazon dot com [this message]
2022-12-01 13:13 ` wilco at gcc dot gnu.org
2022-12-01 16:33 ` rvmallad at amazon dot com
2022-12-02 2:30 ` rvmallad at amazon 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-107413-4-sOSGAYDL9U@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).