public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97496] [11 Regression] during during GIMPLE pass: cddce since r11-4005-g6c6e0cafa38cee83 Date: Mon, 19 Oct 2020 16:15:27 +0000 [thread overview] Message-ID: <bug-97496-4-2ICQwqMZkd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97496-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97496 --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- for SSA_NAME: vect__16.4_34 in statement: # .MEM_29 = VDEF <.MEM_7(D)> MEM <vector(4) int> [(int *)&b] = vect__16.4_34; during GIMPLE pass: slp dump file: pr97496.c.169t.slp1 pr97496.c:3:6: internal compiler error: verify_ssa failed vi 0xfcb522 verify_ssa(bool, bool) /home/marxin/Programming/gcc/gcc/tree-ssa.c:1208 0xcda455 execute_function_todo /home/marxin/Programming/gcc/gcc/passes.c:1999 0xcdb19c do_per_function /home/marxin/Programming/gcc/gcc/passes.c:1640 0xcdb19c execute_todo /home/marxin/Programming/gcc/gcc/passes.c:2046 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:[~2020-10-19 16:15 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-19 16:09 [Bug c/97496] New: ice during during GIMPLE pass: cddce dcb314 at hotmail dot com 2020-10-19 16:15 ` [Bug tree-optimization/97496] [11 Regression] during during GIMPLE pass: cddce since r11-4005-g6c6e0cafa38cee83 marxin at gcc dot gnu.org 2020-10-19 16:15 ` marxin at gcc dot gnu.org [this message] 2020-10-20 6:00 ` rguenth at gcc dot gnu.org 2020-10-20 7:03 ` cvs-commit at gcc dot gnu.org 2020-10-20 7:03 ` 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-97496-4-2ICQwqMZkd@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).