public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dimhen at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/95761] New: [11 regression] ICE during GIMPLE pass: slp verify_ssa failed Date: Fri, 19 Jun 2020 07:25:18 +0000 [thread overview] Message-ID: <bug-95761-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95761 Bug ID: 95761 Summary: [11 regression] ICE during GIMPLE pass: slp verify_ssa failed Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: dimhen at gmail dot com Target Milestone: --- r11-1451 PASS r11-1512 FAIL `gcc -O2' PASS $ gcc -O3 -c x_1.i x_1.i: In function 'k': x_1.i:10:6: error: definition in block 3 follows the use 10 | void k() { | ^ for SSA_NAME: vect__2.17_23 in statement: vect__124.21_25 = vect_cst__58 + vect__2.17_23; during GIMPLE pass: slp x_1.i:10:6: internal compiler error: verify_ssa failed 0x123ff3d verify_ssa(bool, bool) /home/dimhen/src/gcc_current/gcc/tree-ssa.c:1208 0xf37d25 execute_function_todo /home/dimhen/src/gcc_current/gcc/passes.c:1992 0xf38a5c do_per_function /home/dimhen/src/gcc_current/gcc/passes.c:1640 0xf38a5c execute_todo /home/dimhen/src/gcc_current/gcc/passes.c:2039 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. $ cat x_1.i typedef int a[10]; typedef struct { a b; a c; a d; a e; } f; f g; int *j; void k() { for (;;) { a l; j[0] = g.b[0]; int *h = g.d; int i = 0; for (; i < 10; i++) h[i] = l[0] - g.e[0]; h = g.e; i = 0; for (; i < 10; i++) h[i] = l[1] + g.e[i]; } } Sorry for hyper-reduction
next reply other threads:[~2020-06-19 7:25 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-19 7:25 dimhen at gmail dot com [this message] 2020-06-19 7:46 ` [Bug tree-optimization/95761] " rguenth at gcc dot gnu.org 2020-06-19 7:49 ` marxin at gcc dot gnu.org 2020-06-19 11:37 ` cvs-commit at gcc dot gnu.org 2020-06-19 11:37 ` rguenth at gcc dot gnu.org 2020-06-19 17:17 ` dimhen at gmail dot com 2020-06-22 15:36 ` dimhen at gmail dot com 2020-06-23 19:40 ` marxin at gcc dot gnu.org 2020-06-24 6:51 ` dimhen at gmail dot com
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-95761-4@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).