public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115462] New: 416.gamess regressed 4-6% on x86_64 since r15-882-g1d6199e5f8c1c0 Date: Wed, 12 Jun 2024 15:04:26 +0000 [thread overview] Message-ID: <bug-115462-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115462 Bug ID: 115462 Summary: 416.gamess regressed 4-6% on x86_64 since r15-882-g1d6199e5f8c1c0 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jamborm at gcc dot gnu.org CC: crazylht at gmail dot com Blocks: 26163 Target Milestone: --- Benchmark 416.gamess from SPECINT 2006 recently regressed on all x86_64 CPUs we track using many of the compiler options we track. I have bisected the one on Zen3 CPU using -O2 -flto (so -march=generic) to r15-882-g1d6199e5f8c1c0 (liuhongt: Reduce cost of MEM (A + imm)). Regressing hosts and options: - zen2 -O2 -flto: 5% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=292.50.0 - zen2 -O2 -march=native: 6%: https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=291.50.0 - zen2 -O2 -flto -march=native: 5% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=290.50.0 - zen2 -Ofast: 4% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=300.50.0 - skylake -O2: 5% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=784.50.0 - skylake -O2 flto: 4% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=799.50.0 - skylake -O2 -march=native: 6% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=787.50.0 - skylake -O2 -flto -march=native: 5% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=788.50.0 - skylake -Ofast: 4% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=789.50.0 - zen3 -O2 -flto: 5% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=469.50.0 - zen3 -O2 -flto -fprofile-use: 5% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=464.50.0 - zen3 -O2 -flto -march=native: 5% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=465.50.0 - zen3 -Ofast: 5% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=466.50.0 - zen4 -O2 -flto: 4% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=956.50.0 - zen4 -O2 -march=native: 5% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=961.50.0 - zen4 -O2 -flto -march=native: 5% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=993.50.0 - zen4 -Ofast: 4% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=967.50.0 - zen4 -Ofast -march=native: 6% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=965.50.0 - zen4 -Ofast -flto -march=native: 5% https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=992.50.0 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-06-12 15:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-12 15:04 jamborm at gcc dot gnu.org [this message] 2024-06-13 7:24 ` [Bug target/115462] [15 regression] " rguenth at gcc dot gnu.org 2024-06-13 9:09 ` liuhongt at gcc dot gnu.org 2024-06-20 2:00 ` lin1.hu at intel dot com 2024-06-20 6:35 ` lin1.hu at intel dot com 2024-06-27 6:14 ` cvs-commit at gcc dot gnu.org 2024-06-27 6:15 ` liuhongt 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-115462-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).