public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pheeck at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114269] New: [14 Regression] Multiple 3-27% exec time regressions of 434.zeusmp since r14-9193-ga0b1798042d033 Date: Thu, 07 Mar 2024 15:30:54 +0000 [thread overview] Message-ID: <bug-114269-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114269 Bug ID: 114269 Summary: [14 Regression] Multiple 3-27% exec time regressions of 434.zeusmp since r14-9193-ga0b1798042d033 Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: pheeck at gcc dot gnu.org CC: rguenth at gcc dot gnu.org Blocks: 26163 Target Milestone: --- Host: x86_64-linux Target: x86_64-linux Our LNT instance has detected that runtime of benchmark 434.zeusmp from the SPEC 2006 suite regressed on x86_64 machines on most configurations by 3-27%. Some examples: AMD Zen2 -Ofast -march=native -flto (22% regression) https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=289.80.0 Intel Skylake -Ofast -march=native PGO (11% regression) https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=791.80.0 AMD Zen4 -O2 -flto PGO (7% regression) https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=960.80.0 AMD Zen2 -Ofast -march=native (26% regression) https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=301.80.0 I have bisected these configurations to the same commit - AMD Zen2 -Ofast - AMD Zen2 -Ofast -march=native -flto PGO - AMD Zen4 -O2 -flto PGO the commit is r14-9193-ga0b1798042d033 (Richard Biener: tree-optimization/114074 - CHREC multiplication and undefined overflow). I haven't seen this speedup on our Aarch64 machine. I have seen it on our Intel machine though, so this is not an AMD-specific issue. There is another PR where a SPEC slowed down that was also bisected to the same commit: pr114238. Maybe these two PRs are actually the same bug. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163 [Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
next reply other threads:[~2024-03-07 15:30 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-07 15:30 pheeck at gcc dot gnu.org [this message] 2024-03-08 8:18 ` [Bug tree-optimization/114269] " rguenth at gcc dot gnu.org 2024-03-08 10:08 ` xry111 at gcc dot gnu.org 2024-03-08 10:25 ` rguenth at gcc dot gnu.org 2024-03-08 12:23 ` rguenth at gcc dot gnu.org 2024-03-08 13:41 ` cvs-commit at gcc dot gnu.org 2024-03-08 13:41 ` rguenth at gcc dot gnu.org 2024-03-12 12:48 ` [Bug tree-optimization/114269] [14 Regression] Multiple 3-6% " pheeck at gcc dot gnu.org 2024-03-15 15:01 ` law at gcc dot gnu.org 2024-03-19 12:12 ` cvs-commit at gcc dot gnu.org 2024-03-19 12:15 ` rguenth 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-114269-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).