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 tree-optimization/112961] [13 Regression] middle-end Missed vectorization: failed to vectorize simple reduction max since GCC-13
Date: Wed, 13 Dec 2023 07:33:27 +0000	[thread overview]
Message-ID: <bug-112961-4-CTLoNl6XOe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112961-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |ASSIGNED
         Resolution|FIXED                       |---

--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Still eventually for backporting.

  parent reply	other threads:[~2023-12-13  7:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 14:44 [Bug c/112961] New: " juzhe.zhong at rivai dot ai
2023-12-11 15:33 ` [Bug tree-optimization/112961] " pinskia at gcc dot gnu.org
2023-12-11 15:34 ` [Bug tree-optimization/112961] [13/14 Regression] " pinskia at gcc dot gnu.org
2023-12-11 15:34 ` pinskia at gcc dot gnu.org
2023-12-12  7:21 ` rguenth at gcc dot gnu.org
2023-12-12 12:49 ` rguenth at gcc dot gnu.org
2023-12-12 14:14 ` cvs-commit at gcc dot gnu.org
2023-12-12 14:15 ` [Bug tree-optimization/112961] [13 " rguenth at gcc dot gnu.org
2023-12-12 22:50 ` juzhe.zhong at rivai dot ai
2023-12-13  7:33 ` rguenth at gcc dot gnu.org [this message]
2023-12-13  7:35 ` juzhe.zhong at rivai dot ai
2023-12-13  8:44 ` cvs-commit at gcc dot gnu.org
2023-12-13  8:44 ` rguenth at gcc dot gnu.org
2024-05-08 11:50 ` cvs-commit at gcc dot gnu.org
2024-05-08 11:51 ` 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-112961-4-CTLoNl6XOe@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).