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 c/94726] [10/11/12 Regression] ICE in uniform_vector_p, at tree.c:11214 since r10-2089-g21caa1a2649d586f
Date: Thu, 23 Sep 2021 02:12:22 +0000	[thread overview]
Message-ID: <bug-94726-4-mw4hToi0C9@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 #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
After r12-3278-g823685221de986a, the ICE moved slightly:


t.c:13:8: error: conflicting types for ‘a’; have ‘void *[]’
   13 | void * a [ ] = { } ;
      |        ^
t.c:5:6: note: previous declaration of ‘a’ with type ‘type’ {aka ‘__vector(2)
unsigned int’}
    5 | type a , b;
      |      ^
t.c: In function ‘foo’:
t.c:9:13: internal compiler error: tree check: expected class ‘type’, have
‘exceptional’ (error_mark) in create_tmp_from_val, at gimplify.c:568
    9 |         b = __builtin_shuffle ( a , var ) ;
      |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
0x6a9973 tree_class_check_failed(tree_node const*, tree_code_class, char
const*, int, char const*)
        /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/tree.c:8739
0xa9548f tree_class_check(tree_node*, tree_code_class, char const*, int, char
const*)
        /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/tree.h:3546
0xa9548f create_tmp_from_val
        /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/gimplify.c:568
0xa9548f lookup_tmp_var
        /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/gimplify.c:601
0xa9548f internal_get_tmp_var
        /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/gimplify.c:640
0xa98b83 get_initialized_tmp_var(tree_node*, gimple**, gimple**, bool)
        /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/gimplify.c:679
0xa98b83 gimplify_save_expr
        /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/gimplify.c:6251
0xa8f2ff gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
        /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/gimplify.c:14857
0xa8e39b gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
        /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/gimplify.c:15335

  parent reply	other threads:[~2021-09-23  2:12 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 ` pinskia at gcc dot gnu.org [this message]
2021-09-23  2:42 ` [Bug c/94726] [10/11/12 " 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
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-mw4hToi0C9@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).