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 target/113847] [14 Regression] 10% slowdown of 462.libquantum on AMD Ryzen 7700X and Ryzen 7900X
Date: Mon, 12 Feb 2024 14:43:47 +0000	[thread overview]
Message-ID: <bug-113847-4-ZdU0JH8rRH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113847-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113847

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jamborm at gcc dot gnu.org

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
CCing also Martin who should know how/why IPA SRA doesn't reconstruct the
component ref chain here or why it choses the dynamic type as it does
(possibly local SRA when fully scalarizing an aggregate copy does the same).

  parent reply	other threads:[~2024-02-12 14:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09  9:24 [Bug target/113847] New: " fkastl at suse dot cz
2024-02-09 11:13 ` [Bug target/113847] " rguenth at gcc dot gnu.org
2024-02-10 17:04 ` fkastl at suse dot cz
2024-02-12  9:45 ` rguenth at gcc dot gnu.org
2024-02-12 13:18 ` rguenth at gcc dot gnu.org
2024-02-12 14:41 ` rguenth at gcc dot gnu.org
2024-02-12 14:43 ` rguenth at gcc dot gnu.org [this message]
2024-02-12 15:30 ` jamborm at gcc dot gnu.org
2024-03-07 20:40 ` law at gcc dot gnu.org
2024-05-07  7:45 ` [Bug target/113847] [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-113847-4-ZdU0JH8rRH@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).