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 c/94726] [10/11/12 Regression] ICE in uniform_vector_p, at tree.c:11214 since r10-2089-g21caa1a2649d586f
Date: Mon, 27 Sep 2021 10:37:57 +0000	[thread overview]
Message-ID: <bug-94726-4-lSEzuWZaX6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94726-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from CVS 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:76773d3fea4daaaf5b0f6d79d9f48ffe6b3c97fd

commit r12-3896-g76773d3fea4daaaf5b0f6d79d9f48ffe6b3c97fd
Author: Andrew Pinski <apinski@marvell.com>
Date:   Sun Sep 26 05:44:58 2021 +0000

    Fix PR c/94726: ICE with __builtin_shuffle and changing of types

    The problem here is __builtin_shuffle when called with two arguments
    instead of 1, uses a SAVE_EXPR to put in for the 1st and 2nd operand
    of VEC_PERM_EXPR and when we go and gimplify the SAVE_EXPR, the type
    is now error_mark_node and that fails hard.
    This fixes the problem by adding a simple check for type of operand
    of SAVE_EXPR not to be error_mark_node.

    OK? Bootstrapped and tested on aarch64-linux-gnu with no regressions.

    gcc/ChangeLog:

            PR c/94726
            * gimplify.c (gimplify_save_expr): Return early
            if the type of val is error_mark_node.

    gcc/testsuite/ChangeLog:

            PR c/94726
            * gcc.dg/pr94726.c: New test.

  parent reply	other threads:[~2021-09-27 10:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23  2:56 [Bug c/94726] New: internal compiler error: in uniform_vector_p, at tree.c:11214 anbu1024.me at gmail dot com
2020-04-23  5:24 ` [Bug middle-end/94726] [10 Regression] internal compiler error: in uniform_vector_p, at tree.c:11214 since r10-2089-g21caa1a2649d586f marxin at gcc dot gnu.org
2020-04-24  8:59 ` [Bug c/94726] [10 Regression] ICE " rguenth at gcc dot gnu.org
2020-04-24  9:20 ` marxin at gcc dot gnu.org
2020-04-24 10:59 ` jakub at gcc dot gnu.org
2020-05-07 11:56 ` [Bug c/94726] [10/11 " jakub at gcc dot gnu.org
2020-07-23  6:51 ` rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-09-23  2:12 ` [Bug c/94726] [10/11/12 " pinskia at gcc dot gnu.org
2021-09-23  2:42 ` pinskia at gcc dot gnu.org
2021-09-26 10:00 ` pinskia at gcc dot gnu.org
2021-09-27 10:37 ` cvs-commit at gcc dot gnu.org [this message]
2021-09-27 10:41 ` 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-94726-4-lSEzuWZaX6@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).