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/109747] [12/13 Regression] SLP cost of constructors is off
Date: Tue, 23 May 2023 17:00:12 +0000	[thread overview]
Message-ID: <bug-109747-4-3ZUn4iEhSD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109747-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[12/13/14 Regression] SLP   |[12/13 Regression] SLP cost
                   |cost of constructors is off |of constructors is off
      Known to work|                            |14.0
           Priority|P3                          |P2

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed on trunk sofar.  Note fixing on the branch(es) will eventually cause more
SLP vectorization which isn't always desired.  So I'm at least waiting for
regressions on trunk because of this.

      parent reply	other threads:[~2023-05-23 17:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 11:56 [Bug target/109747] New: [12/13/14 " rguenth at gcc dot gnu.org
2023-05-05 12:02 ` [Bug target/109747] " rguenth at gcc dot gnu.org
2023-05-08 12:27 ` rguenth at gcc dot gnu.org
2023-05-09 11:05 ` rguenth at gcc dot gnu.org
2023-05-23 16:59 ` cvs-commit at gcc dot gnu.org
2023-05-23 17:00 ` rguenth at gcc dot gnu.org [this message]

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-109747-4-3ZUn4iEhSD@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).