public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/109858] New: r14-172 caused some SPEC2017 bmk to degrade on Power
Date: Mon, 15 May 2023 02:06:56 +0000 [thread overview]
Message-ID: <bug-109858-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109858
Bug ID: 109858
Summary: r14-172 caused some SPEC2017 bmk to degrade on Power
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: linkw at gcc dot gnu.org
Target Milestone: ---
On Power9,
- at option -Ofast, 557.xz_r degraded -1.06%.
- at option -Ofast, 511.povray_r degraded -1.24%.
On Power10,
- at option -O2, 520.omnetpp_r degraded -1.84%.
I tried to run them in a few times, the gaps are stable. I've excluded those
one in +-1% as noises. The full data is listed below:
P9 O2:
500.perlbench_r 0.00%
502.gcc_r -0.20%
505.mcf_r 0.00%
520.omnetpp_r -0.30%
523.xalancbmk_r 0.00%
525.x264_r 0.00%
531.deepsjeng_r 0.00%
541.leela_r 0.00%
548.exchange2_r 0.00%
557.xz_r 0.00%
503.bwaves_r 0.00%
507.cactuBSSN_r 0.00%
508.namd_r -0.32%
510.parest_r 0.00%
511.povray_r 0.32%
519.lbm_r -0.16%
521.wrf_r 0.00%
526.blender_r 0.27%
527.cam4_r 0.00%
538.imagick_r 0.00%
544.nab_r 0.00%
549.fotonik3d_r 0.00%
554.roms_r 0.00%
P9 Ofast:
500.perlbench_r 0.00%
502.gcc_r 0.00%
505.mcf_r 0.00%
520.omnetpp_r 0.00%
523.xalancbmk_r 0.00%
525.x264_r 0.17%
531.deepsjeng_r 0.00%
541.leela_r 0.00%
548.exchange2_r 2.15%
557.xz_r -1.06%
503.bwaves_r 2.21%
507.cactuBSSN_r -0.20%
508.namd_r -0.33%
510.parest_r 0.00%
511.povray_r -1.24%
519.lbm_r 0.00%
521.wrf_r 0.19%
526.blender_r 0.00%
527.cam4_r 0.28%
538.imagick_r 0.32%
544.nab_r 0.00%
549.fotonik3d_r -0.83%
554.roms_r 1.33%
Power10 O2:
500.perlbench_r 0.00%
502.gcc_r 0.33%
505.mcf_r 0.55%
520.omnetpp_r -1.84%
523.xalancbmk_r 0.00%
525.x264_r 0.36%
531.deepsjeng_r 0.00%
541.leela_r 0.00%
548.exchange2_r 0.00%
557.xz_r 0.31%
503.bwaves_r 0.00%
507.cactuBSSN_r -0.31%
508.namd_r -0.22%
510.parest_r -0.64%
511.povray_r -0.86%
519.lbm_r -0.75%
521.wrf_r 0.20%
526.blender_r 0.20%
527.cam4_r 0.00%
538.imagick_r -0.15%
544.nab_r -0.18%
549.fotonik3d_r 0.00%
554.roms_r 0.00%
Power10 Ofast:
502.gcc_r 0.16%
505.mcf_r 0.00%
520.omnetpp_r 0.00%
523.xalancbmk_r 0.22%
525.x264_r 0.30%
531.deepsjeng_r 0.00%
541.leela_r 0.00%
548.exchange2_r 0.00%
557.xz_r 0.31%
503.bwaves_r -0.18%
507.cactuBSSN_r 0.00%
508.namd_r 0.22%
510.parest_r -0.52%
511.povray_r 0.00%
519.lbm_r 0.50%
521.wrf_r 0.00%
526.blender_r -0.80%
527.cam4_r 0.18%
538.imagick_r -0.11%
544.nab_r 0.17%
549.fotonik3d_r 0.63%
554.roms_r -0.63%
next reply other threads:[~2023-05-15 2:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 2:06 linkw at gcc dot gnu.org [this message]
2023-05-15 2:24 ` [Bug rtl-optimization/109858] " pinskia at gcc dot gnu.org
2023-05-15 2:25 ` pinskia at gcc dot gnu.org
2023-05-15 7:43 ` [Bug rtl-optimization/109858] [14 Regression] " crazylht at gmail dot com
2023-05-15 9:40 ` linkw at gcc dot gnu.org
2023-05-16 2:50 ` crazylht at gmail dot com
2023-05-16 2:53 ` crazylht at gmail dot com
2023-05-16 3:08 ` linkw at gcc dot gnu.org
2023-05-16 15:17 ` segher at gcc dot gnu.org
2023-05-17 1:25 ` crazylht at gmail dot com
2023-05-17 5:21 ` linkw at gcc dot gnu.org
2023-05-17 14:48 ` segher at gcc dot gnu.org
2023-05-26 1:46 ` cvs-commit at gcc dot gnu.org
2023-06-20 10:35 ` linkw at gcc dot gnu.org
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-109858-4@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).