public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110973] 9% 444.namd regression between g:c2a447d840476dbd (2023-08-03 18:47) and g:73da34a538ddc2ad (2023-08-09 20:17)
Date: Fri, 11 Aug 2023 13:33:24 +0000 [thread overview]
Message-ID: <bug-110973-4-NNjZ4ysET0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110973-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110973
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization,
| |needs-bisection
Target| |x86_64-*-*
CC| |rguenth at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=110972
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Probably the same cause as PR110972, but I can only confirm a 2.5% regression
on Zen2 due to r14-3078-gd9f3ea61fe36e2. Looks like the bigger regression was
for generic? I can confirm a 5.5% regression for -Ofast generic on Zen2 due to
r14-3078-gd9f3ea61fe36e2.
next prev parent reply other threads:[~2023-08-11 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 14:47 [Bug middle-end/110973] New: 9% namd " hubicka at gcc dot gnu.org
2023-08-11 13:33 ` rguenth at gcc dot gnu.org [this message]
2023-08-11 13:56 ` [Bug middle-end/110973] 9% 444.namd " rguenth at gcc dot gnu.org
2023-08-24 15:41 ` jamborm at gcc dot gnu.org
2023-08-25 11:52 ` fkastl at suse dot cz
2023-08-29 9:11 ` hubicka at gcc dot gnu.org
2023-08-29 9:28 ` rguenth at gcc dot gnu.org
2023-08-29 9:59 ` fkastl at suse dot cz
2023-08-29 14:43 ` fkastl at suse dot cz
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-110973-4-NNjZ4ysET0@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).