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 tree-optimization/111972] [14 regression] missed vectorzation for bool a = j != 1; j = (long int)a;
Date: Sun, 10 Dec 2023 20:04:03 +0000	[thread overview]
Message-ID: <bug-111972-4-nikbsGj5HG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111972-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |patch
                URL|                            |https://gcc.gnu.org/piperma
                   |                            |il/gcc-patches/2023-Decembe
                   |                            |r/640064.html

--- Comment #17 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Updated patch set:
https://gcc.gnu.org/pipermail/gcc-patches/2023-December/640064.html

The first patch of the original patch set was applied.

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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25  8:14 [Bug middle-end/111972] New: " crazylht at gmail dot com
2023-10-25  9:29 ` [Bug tree-optimization/111972] " crazylht at gmail dot com
2023-10-25 16:46 ` pinskia at gcc dot gnu.org
2023-10-27  3:48 ` pinskia at gcc dot gnu.org
2023-10-27  3:59 ` pinskia at gcc dot gnu.org
2023-10-27  4:01 ` pinskia at gcc dot gnu.org
2023-10-27  5:08 ` crazylht at gmail dot com
2023-10-27  5:17 ` crazylht at gmail dot com
2023-10-27  6:08 ` pinskia at gcc dot gnu.org
2023-10-27  6:11 ` pinskia at gcc dot gnu.org
2023-10-27 12:38 ` rguenth at gcc dot gnu.org
2023-11-14  1:28 ` cvs-commit at gcc dot gnu.org
2023-11-21  1:00 ` liuhongt at gcc dot gnu.org
2023-11-21  1:12 ` pinskia at gcc dot gnu.org
2023-11-21  2:48 ` liuhongt at gcc dot gnu.org
2023-12-02  6:38 ` pinskia at gcc dot gnu.org
2023-12-04 17:31 ` cvs-commit at gcc dot gnu.org
2023-12-10 20:04 ` pinskia at gcc dot gnu.org [this message]
2023-12-11 15:56 ` cvs-commit at gcc dot gnu.org
2023-12-11 15:57 ` pinskia at gcc dot gnu.org
2023-12-12  2:58 ` liuhongt 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-111972-4-nikbsGj5HG@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).