public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110757] New: 7% parest regression on zen3 -Ofast -march=native -flto between g:4dbb3af1efe55174 (2023-07-14 00:54) and g:a5088dc3f5ef73c8 (2023-07-17 03:24)
Date: Thu, 20 Jul 2023 21:55:47 +0000 [thread overview]
Message-ID: <bug-110757-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110757
Bug ID: 110757
Summary: 7% parest regression on zen3 -Ofast -march=native
-flto between g:4dbb3af1efe55174 (2023-07-14 00:54)
and g:a5088dc3f5ef73c8 (2023-07-17 03:24)
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: hubicka at gcc dot gnu.org
Target Milestone: ---
seems there are two commits producing this regression. Run in between is
d76d19c9bc5ef113 (2023-07-16 00:16)
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=475.457.0
There are earlier two jumps between g:52577a301ef1b86d (2023-05-30 02:20) and
g:d0c064c3eabc75cf (2023-05-31 16:46)
and between g:7ebd4a1d61993c0a (2023-04-28 07:23) and g:977a3be3ccbc7f17
(2023-05-01 13:40)
8% regression is also seen on zen1 machine:
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=287.457.0
next reply other threads:[~2023-07-20 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 21:55 hubicka at gcc dot gnu.org [this message]
2023-07-20 21:58 ` [Bug middle-end/110757] [14 Regression] " pinskia at gcc dot gnu.org
2023-07-21 17:17 ` jamborm at gcc dot gnu.org
2023-07-21 19:14 ` jamborm at gcc dot gnu.org
2023-07-22 11:41 ` jamborm at gcc dot gnu.org
2023-07-26 7:15 ` hubicka at gcc dot gnu.org
2024-03-07 23:28 ` law at gcc dot gnu.org
2024-05-07 7:41 ` [Bug middle-end/110757] [14/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-110757-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: 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).