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/114281] New: [14 Regression] Multiple 2-10% exec time regressions of 465.tonto since r14-9193-ga0b1798042d033 Date: Fri, 08 Mar 2024 09:33:13 +0000 [thread overview] Message-ID: <bug-114281-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114281 Bug ID: 114281 Summary: [14 Regression] Multiple 2-10% exec time regressions of 465.tonto 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 Blocks: 26163 Target Milestone: --- Host: aarch64-gnu-linux, x86_64-linux Target: aarch64-gnu-linux, x86_64-linux Our LNT instance has detected that runtime of benchmark 465.tonto from the SPEC 2006 suite regressed on all of our machines (aarch64 ampere altra, intel skylake, amd zen{2,3,4}) on most configurations by 2-10%. One example: Zen4 -Ofast -flto -march=native (regressed by 10%) https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=992.230.0 I've bisected the example configuration to r14-9193-ga0b1798042d033 (Richard Biener: tree-optimization/114074 - CHREC multiplication and undefined overflow). There have been two other SPEC benchmarks regressions reported that also got bisected to this commit -- pr114269, pr114238. I assume that all of these have the same cause. 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-08 9:33 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-08 9:33 pheeck at gcc dot gnu.org [this message] 2024-03-08 10:08 ` [Bug tree-optimization/114281] " xry111 at gcc dot gnu.org 2024-03-08 10:17 ` pheeck 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-114281-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).