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] [14 Regression] Multiple 3-6% exec time regressions of 434.zeusmp since r14-9193-ga0b1798042d033
Date: Tue, 12 Mar 2024 12:48:35 +0000 [thread overview]
Message-ID: <bug-114269-4-iXMKPPPmjw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114269-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114269
Filip Kastl <pheeck at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|RESOLVED |REOPENED
Summary|[14 Regression] Multiple |[14 Regression] Multiple
|3-27% exec time regressions |3-6% exec time regressions
|of 434.zeusmp since |of 434.zeusmp since
|r14-9193-ga0b1798042d033 |r14-9193-ga0b1798042d033
--- Comment #7 from Filip Kastl <pheeck at gcc dot gnu.org> ---
Nice, our LNT instance already shows that the patch sped up 434.zeusmp. However
I'd like to reopen this bug since the benchmark didn't return to its original
values. At least some configurations are still slower than before
r14-9193-ga0b1798042d033:
Intel Skylake -Ofast -march=native (~5% regression)
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=798.80.0
Intel Skylake -Ofast -march=native -flto PGO (~5% regression)
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=785.80.0
AMD Zen3 -Ofast -march=native -flto (~6% regression)
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=476.80.0
AMD Zen3 -Ofast -march=native -flto PGO (~4% regression)
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=474.80.0
AMD Zen2 -Ofast -march=native -flto (~3% regression)
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=289.80.0
next prev parent reply other threads:[~2024-03-12 12:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 15:30 [Bug tree-optimization/114269] New: [14 Regression] Multiple 3-27% " pheeck at gcc dot gnu.org
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 ` pheeck at gcc dot gnu.org [this message]
2024-03-15 15:01 ` [Bug tree-optimization/114269] [14 Regression] Multiple 3-6% " 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-iXMKPPPmjw@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).