public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110506] [14 Regression] Ice: tree check: expected none of vector_type, have vector_type in get_value_for_expr, at tree-ssa-ccp.cc:686 Date: Sat, 01 Jul 2023 08:15:25 +0000 [thread overview] Message-ID: <bug-110506-4-96xQdaQB1W@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110506-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110506 --- Comment #4 from David Binderman <dcb314 at hotmail dot com> --- This C code might be related: typedef unsigned uint32_t; typedef uint32_t uint32x4 __attribute__((vector_size(16))); typedef struct { uint32x4 b, d } prng_t; prng_t prng_rand_128_r_x; main_flags; main() { uint32_t ref_crc[] = {7, 3}; uint32x4 e = (prng_rand_128_r_x.b << 27) + (prng_rand_128_r_x.b >> 32 - 27); prng_rand_128_r_x.d = e; if (ref_crc[main_flags]) __assert_fail(); } $ ~/gcc/results/bin/gcc -c -w -O2 bug936B.c during GIMPLE pass: slp bug936B.c: In function ‘main’: bug936B.c:8:1: internal compiler error: tree check: expected none of vector_type , have vector_type in vect_recog_rotate_pattern, at tree-vect-patterns.cc:3729 8 | main() { | ^~~~ 0x1166129 tree_not_check_failed(tree_node const*, char const*, int, char const*, ...) ../../trunk.year/gcc/tree.cc:8936 0x1cc8da3 vect_recog_rotate_pattern(vec_info*, _stmt_vec_info*, tree_node**) ../../trunk.year/gcc/tree-vect-patterns.cc:0
next prev parent reply other threads:[~2023-07-01 8:15 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-30 17:43 [Bug c/110506] New: ice: " dcb314 at hotmail dot com 2023-06-30 19:31 ` [Bug tree-optimization/110506] [14 Regression] Ice: " pinskia at gcc dot gnu.org 2023-06-30 19:38 ` pinskia at gcc dot gnu.org 2023-06-30 20:13 ` pinskia at gcc dot gnu.org 2023-06-30 20:14 ` pinskia at gcc dot gnu.org 2023-07-01 8:15 ` dcb314 at hotmail dot com [this message] 2023-07-03 6:25 ` rguenth at gcc dot gnu.org 2023-07-03 8:05 ` cvs-commit at gcc dot gnu.org 2023-07-03 8:05 ` cvs-commit at gcc dot gnu.org 2023-07-03 8:06 ` rguenth 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-110506-4-96xQdaQB1W@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).