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] New: Perf loss ~14% on 519.lbm_r SPEC cpu2017 benchmark Date: Wed, 26 Oct 2022 09:16:04 +0000 [thread overview] Message-ID: <bug-107413-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107413 Bug ID: 107413 Summary: Perf loss ~14% on 519.lbm_r SPEC cpu2017 benchmark Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: rvmallad at amazon dot com Target Milestone: --- Created attachment 53775 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53775&action=edit Input and source files. Below is some perf data executing the 519.lbm_r benchmark on aarch64 architecture (Graviton 3 processor). I have comparison of the baseline perf (mainline commit ID: f56d48b2471c388401174029324e1f4c4b84fcdb) vs. a fix for the same (revert the code change in commit ID: b5b33e113434be909e8a6d7b93824196fb6925c0). Steps to compile: $ gcc -std=c99 -mabi=lp64 -g -Ofast -mcpu=native lbm.i main.i -lm -flto -o 519_lbm_r_base $ time ./519_lbm_r_base 3000 reference.dat 0 0 100_100_130_ldc.of real 2m50.946s Reverting the code changes in commit ID: b5b33e113434be909e8a6d7b93824196fb6925c0 $ time ./519_lbm_r_fix 3000 reference.dat 0 0 100_100_130_ldc.of real 2m27.157s The code change reverted was: [AArch64] PR84114: Avoid reassociating FMA Author: Wilco Dijkstra <wdijkstr@arm.com> Date: Mon Mar 5 14:40:55 2018 +0000 Please find attached the files to reproduce this issue and the fix.
next reply other threads:[~2022-10-26 9:16 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-26 9:16 rvmallad at amazon dot com [this message] 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 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@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: linkBe 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).