public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101112] New: [12 regression] ICE compiling gcc.dg/pr86179.c after r12-1551 Date: Thu, 17 Jun 2021 19:15:53 +0000 [thread overview] Message-ID: <bug-101112-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101112 Bug ID: 101112 Summary: [12 regression] ICE compiling gcc.dg/pr86179.c after r12-1551 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:3dfa4fe9f1a089b2b3906c83e22a1b39c49d937c, r12-1551 make -k check-gcc RUNTESTFLAGS="dg.exp=gcc.dg/pr86179.c" FAIL: gcc.dg/pr86179.c (internal compiler error) FAIL: gcc.dg/pr86179.c (test for excess errors) # of unexpected failures 2 Executing on host: /home/seurer/gcc/git/build/gcc-test/gcc/xgcc -B/home/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled731.cc -fdiagnostics-plain-output -S -o exceptions_enabled731.s (timeout = 300) spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc -B/home/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled731.cc -fdiagnostics-plain-output -S -o exceptions_enabled731.s FAIL: gcc.dg/pr86179.c (test for excess errors) Excess errors: during GIMPLE pass: vect /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/pr86179.c:7:6: internal compiler error: in vect_slp_analyze_node_operations, at tree-vect-slp.c:4541 0x10f66307 vect_slp_analyze_node_operations /home/seurer/gcc/git/gcc-test/gcc/tree-vect-slp.c:4539 0x10f65993 vect_slp_analyze_node_operations /home/seurer/gcc/git/gcc-test/gcc/tree-vect-slp.c:4482 0x10f65993 vect_slp_analyze_node_operations /home/seurer/gcc/git/gcc-test/gcc/tree-vect-slp.c:4482 0x10f65993 vect_slp_analyze_node_operations /home/seurer/gcc/git/gcc-test/gcc/tree-vect-slp.c:4482 0x10f65993 vect_slp_analyze_node_operations /home/seurer/gcc/git/gcc-test/gcc/tree-vect-slp.c:4482 0x10f68667 vect_slp_analyze_operations(vec_info*) /home/seurer/gcc/git/gcc-test/gcc/tree-vect-slp.c:4737 0x10f381fb vect_analyze_loop_2 /home/seurer/gcc/git/gcc-test/gcc/tree-vect-loop.c:2396 0x10f3a5c7 vect_analyze_loop(loop*, vec_info_shared*) /home/seurer/gcc/git/gcc-test/gcc/tree-vect-loop.c:2986 0x10f7c25f try_vectorize_loop_1 /home/seurer/gcc/git/gcc-test/gcc/tree-vectorizer.c:1004 0x10f7d14f vectorize_loops() /home/seurer/gcc/git/gcc-test/gcc/tree-vectorizer.c:1238 0x10dbde47 execute /home/seurer/gcc/git/gcc-test/gcc/tree-ssa-loop.c:414 commit 3dfa4fe9f1a089b2b3906c83e22a1b39c49d937c Author: Richard Biener <rguenther@suse.de> Date: Tue Jun 8 15:10:45 2021 +0200
next reply other threads:[~2021-06-17 19:15 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-17 19:15 seurer at gcc dot gnu.org [this message] 2021-06-17 22:48 ` [Bug tree-optimization/101112] " pinskia at gcc dot gnu.org 2021-06-17 22:48 ` pinskia at gcc dot gnu.org 2021-06-18 9:50 ` rguenth at gcc dot gnu.org 2021-06-18 9:58 ` rguenth at gcc dot gnu.org 2021-06-18 11:43 ` cvs-commit at gcc dot gnu.org 2021-06-18 11:45 ` rguenth at gcc dot gnu.org 2021-06-18 13:31 ` 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-101112-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).