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/110817] [14 Regression] wrong code with vector compares and vector lowering
Date: Tue, 17 Oct 2023 12:17:04 +0000	[thread overview]
Message-ID: <bug-110817-4-B4It7KktPX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110817-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P1

--- Comment #22 from Richard Biener <rguenth at gcc dot gnu.org> ---
Patch was approved I think?

  parent reply	other threads:[~2023-10-17 12:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 15:42 [Bug tree-optimization/110817] New: [14 Regression] wrong code with vector compares on multiple targets zsojka at seznam dot cz
2023-07-26 17:44 ` [Bug tree-optimization/110817] " pinskia at gcc dot gnu.org
2023-07-26 17:57 ` [Bug tree-optimization/110817] [14 Regression] wrong code with vector compares and vector lowering pinskia at gcc dot gnu.org
2023-07-27  7:26 ` rguenth at gcc dot gnu.org
2023-07-27  7:57 ` pinskia at gcc dot gnu.org
2023-07-27  7:59 ` pinskia at gcc dot gnu.org
2023-07-27  8:06 ` pinskia at gcc dot gnu.org
2023-07-27  8:16 ` pinskia at gcc dot gnu.org
2023-07-27  8:26 ` pinskia at gcc dot gnu.org
2023-07-27 20:42 ` pinskia at gcc dot gnu.org
2023-09-01 10:29 ` zsojka at seznam dot cz
2023-09-01 10:34 ` pinskia at gcc dot gnu.org
2023-09-01 11:07 ` zsojka at seznam dot cz
2023-09-01 20:17 ` pinskia at gcc dot gnu.org
2023-09-01 20:45 ` pinskia at gcc dot gnu.org
2023-09-01 20:48 ` pinskia at gcc dot gnu.org
2023-09-01 21:02 ` pinskia at gcc dot gnu.org
2023-09-01 21:40 ` pinskia at gcc dot gnu.org
2023-09-01 21:53 ` pinskia at gcc dot gnu.org
2023-09-02  1:09 ` pinskia at gcc dot gnu.org
2023-09-02  2:33 ` pinskia at gcc dot gnu.org
2023-09-22  5:21 ` pinskia at gcc dot gnu.org
2023-10-17 12:17 ` rguenth at gcc dot gnu.org [this message]
2023-10-17 22:44 ` cvs-commit at gcc dot gnu.org
2023-10-17 22:44 ` pinskia 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-110817-4-B4It7KktPX@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).