public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110757] [14 Regression] 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:58:58 +0000 [thread overview]
Message-ID: <bug-110757-4-5bjGhFsYdK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110757-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110757
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Summary|7% parest regression on |[14 Regression] 7% parest
|zen3 -Ofast -march=native |regression on zen3 -Ofast
|-flto between |-march=native -flto between
|g:4dbb3af1efe55174 |g:4dbb3af1efe55174
|(2023-07-14 00:54) and |(2023-07-14 00:54) and
|g:a5088dc3f5ef73c8 |g:a5088dc3f5ef73c8
|(2023-07-17 03:24) |(2023-07-17 03:24)
Target Milestone|--- |14.0
CC| |pinskia at gcc dot gnu.org
Version|13.1.0 |14.0
next prev parent reply other threads:[~2023-07-20 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 21:55 [Bug middle-end/110757] New: " hubicka at gcc dot gnu.org
2023-07-20 21:58 ` pinskia at gcc dot gnu.org [this message]
2023-07-21 17:17 ` [Bug middle-end/110757] [14 Regression] " 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-5bjGhFsYdK@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).