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/104499] [12 Regression] ICE: in emit_move_insn, at expr.cc:4010 at -O1
Date: Fri, 11 Feb 2022 19:27:44 +0000	[thread overview]
Message-ID: <bug-104499-4-nTsTZQLNn8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104499-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:9355a8c35883b5125851bb9b4169a1a1cd8e343f

commit r12-7202-g9355a8c35883b5125851bb9b4169a1a1cd8e343f
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Feb 11 20:27:23 2022 +0100

    match.pd: Fix up (X & Y) CMP 0 -> X CMP2 ~Y simplifications [PR104499]

    The following testcase ICEs on x86_64-linux, because match.pd emits
    there a NOP_EXPR cast from int*8 vector type with BLKmode to
    unsigned*8 vector type with BLKmode and vec-lowering isn't prepared
    to handle such casts.

    Fixed by using VIEW_CONVERT_EXPR instead.

    2022-02-11  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/104499
            * match.pd ((X & Y) CMP 0 -> X CMP2 ~Y): Use view_convert instead
            of convert.

            * gcc.c-torture/compile/pr104499.c: New test.

  parent reply	other threads:[~2022-02-11 19:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 11:04 [Bug rtl-optimization/104499] New: " zsojka at seznam dot cz
2022-02-11 12:38 ` [Bug rtl-optimization/104499] " jakub at gcc dot gnu.org
2022-02-11 12:50 ` [Bug tree-optimization/104499] " jakub at gcc dot gnu.org
2022-02-11 19:27 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-11 19:29 ` jakub 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-104499-4-nTsTZQLNn8@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).