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 middle-end/102029] [12 Regression] ice:  error: type mismatch in ‘lshift_expr’
Date: Tue, 24 Aug 2021 02:00:12 +0000	[thread overview]
Message-ID: <bug-102029-4-XUGpTlyWhG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102029-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>:

https://gcc.gnu.org/g:78fa5112b4c2dcd94b78ee79baddebbf14d6ad98

commit r12-3104-g78fa5112b4c2dcd94b78ee79baddebbf14d6ad98
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Tue Aug 24 02:59:02 2021 +0100

    [Committed] PR middle-end/102029: Stricter typing in LSHIFT_EXPR sign
folding.

    My sincere apologies to everyone (again).  As diagnosed by
    Jakub Jelinek, my recent patch to fold the signedness of LSHIFT_EXPR
    needs to be careful not to attempt transforming a left shift in an
    integer type into an invalid left shift of a pointer type.

    2021-08-24  Roger Sayle  <roger@nextmovesoftware.com>
                Jakub Jelinek  <jakub@redhat.com>

    gcc/ChangeLog
            PR middle-end/102029
            * match.pd (shift transformations): Add an additional check for
            !POINTER_TYPE_P in the recently added left shift transformation.

    gcc/testsuite/ChangeLog
            PR middle-end/102029
            * gcc.dg/fold-convlshift-3.c: New test case.

  parent reply	other threads:[~2021-08-24  2:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 19:47 [Bug c/102029] New: " dcb314 at hotmail dot com
2021-08-23 19:50 ` [Bug middle-end/102029] [12 Regression] " pinskia at gcc dot gnu.org
2021-08-23 19:51 ` pinskia at gcc dot gnu.org
2021-08-23 20:21 ` jakub at gcc dot gnu.org
2021-08-23 21:52 ` roger at nextmovesoftware dot com
2021-08-24  2:00 ` cvs-commit at gcc dot gnu.org [this message]
2021-08-24  7:14 ` rguenth at gcc dot gnu.org
2021-08-24 12:23 ` dje at gcc dot gnu.org
2021-08-26 17:52 ` cvs-commit 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-102029-4-XUGpTlyWhG@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).