public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/112738] [14 Regression] forwprop4 introduces invalid wide signed Boolean values
Date: Tue, 28 Nov 2023 17:52:36 +0000	[thread overview]
Message-ID: <bug-112738-4-eQWLNpQ4cz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112738-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:

https://gcc.gnu.org/g:68ffaf839883253e0f288862ff20b8005c92df4e

commit r14-5938-g68ffaf839883253e0f288862ff20b8005c92df4e
Author: Andrew Pinski <quic_apinski@quicinc.com>
Date:   Mon Nov 27 16:41:25 2023 -0800

    MATCH: Fix invalid signed boolean type usage

    This fixes the incorrect assumption that was done in
r14-3721-ge6bcf839894783,
    that being able to doing the negative after the conversion would be a valid
thing
    but really it is not valid for boolean types.

    Bootstrapped and tested on x86_64-linux-gnu.

    gcc/ChangeLog:

            PR tree-optimization/112738
            * match.pd (`(nop_convert)-(convert)a`): Reject
            when the outer type is boolean.

    Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>

  parent reply	other threads:[~2023-11-28 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 23:21 [Bug tree-optimization/112738] New: " kristerw at gcc dot gnu.org
2023-11-27 23:26 ` [Bug tree-optimization/112738] [14 Regression] " pinskia at gcc dot gnu.org
2023-11-27 23:34 ` pinskia at gcc dot gnu.org
2023-11-28 17:52 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-28 17:52 ` 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-112738-4-eQWLNpQ4cz@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).