public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100887] [12 Regression] ICE: in ix86_expand_vector_init_concat, at config/i386/i386-expand.c:14178 with -mavx512f and __builtin_shufflevector() Date: Thu, 03 Jun 2021 10:40:52 +0000 [thread overview] Message-ID: <bug-100887-4-tGoLHDjCid@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100887-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100887 --- Comment #3 from Zdenek Sojka <zsojka at seznam dot cz> --- Probably related issue: $ cat testcase.c typedef unsigned long long __attribute__((__vector_size__ (16))) U; typedef unsigned long long __attribute__((__vector_size__ (32))) V; typedef unsigned long long __attribute__((__vector_size__ (64))) W; U foo (V v) { return __builtin_shufflevector ((W){}, v, 0, 8); } $ x86_64-pc-linux-gnu-gcc -mavx512f testcase.c testcase.c: In function 'foo': testcase.c:6:1: error: not allowed type combination in 'bit_insert_expr' 6 | foo (V v) | ^~~ W V _2 = BIT_INSERT_EXPR <{ 0, 0, 0, 0, 0, 0, 0, 0 }, v, 64>; testcase.c:6:1: internal compiler error: 'verify_gimple' failed 0x10b85ad verify_gimple_in_seq(gimple*) /repo/gcc-trunk/gcc/tree-cfg.c:5161 0xdaf5e6 gimplify_body(tree_node*, bool) /repo/gcc-trunk/gcc/gimplify.c:15404 0xdaf75d gimplify_function_tree(tree_node*) /repo/gcc-trunk/gcc/gimplify.c:15475 0xbd9127 cgraph_node::analyze() /repo/gcc-trunk/gcc/cgraphunit.c:670 0xbdbc57 analyze_functions /repo/gcc-trunk/gcc/cgraphunit.c:1234 0xbdc8ed symbol_table::finalize_compilation_unit() /repo/gcc-trunk/gcc/cgraphunit.c:2508 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next prev parent reply other threads:[~2021-06-03 10:40 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-02 20:59 [Bug target/100887] New: " zsojka at seznam dot cz 2021-06-03 9:59 ` [Bug target/100887] " jakub at gcc dot gnu.org 2021-06-03 10:08 ` jakub at gcc dot gnu.org 2021-06-03 10:40 ` zsojka at seznam dot cz [this message] 2021-06-03 10:41 ` zsojka at seznam dot cz 2021-06-03 10:47 ` jakub at gcc dot gnu.org 2021-06-03 10:48 ` zsojka at seznam dot cz 2021-06-03 13:18 ` jakub at gcc dot gnu.org 2021-06-04 9:20 ` cvs-commit at gcc dot gnu.org 2021-06-07 7:29 ` cvs-commit at gcc dot gnu.org 2021-06-07 7:37 ` jakub at gcc dot gnu.org 2021-06-08 8:07 ` cvs-commit at gcc dot gnu.org 2021-06-17 5:59 ` cvs-commit at gcc dot gnu.org 2021-06-17 5:59 ` cvs-commit at gcc dot gnu.org 2022-05-10 8:18 ` cvs-commit at gcc dot gnu.org 2022-05-10 8:18 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:20 ` 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-100887-4-tGoLHDjCid@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: linkBe 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).