public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108314] New: [13 Regression] Segfault in gimple-match-head.cc:do_valueize when vectorizing for SVE Date: Fri, 06 Jan 2023 10:38:57 +0000 [thread overview] Message-ID: <bug-108314-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108314 Bug ID: 108314 Summary: [13 Regression] Segfault in gimple-match-head.cc:do_valueize when vectorizing for SVE Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: acoplan at gcc dot gnu.org Target Milestone: --- The following appears to be a regression on the trunk: $ cat t.c int x, y, z; void f(void) { int t = 4; for (; x; x++) { if (y) continue; t = 0; } z = t; } $ aarch64-none-elf-gcc -c t.c -O2 -march=armv9-a during GIMPLE pass: vect t.c: In function 'f': t.c:2:6: internal compiler error: Segmentation fault 2 | void f(void) { | ^ 0xed3a4f crash_signal /home/alecop01/toolchain/src/gcc/gcc/toplev.cc:314 0x17255c4 do_valueize /home/alecop01/toolchain/src/gcc/gcc/gimple-match-head.cc:845 0x17255c4 operator() /home/alecop01/toolchain/src/gcc/gcc/gimple-match-head.cc:1071 0x17255c4 gimple_extract<gimple_simplify(gimple*, gimple_match_op*, gimple**, tree_node* (*)(tree), tree_node* (*)(tree))::<lambda(tree)>, gimple_simplify(gimple*, gimple_match_op*, gimple**, tree_node* (*)(tree), tree_node* (*)(tree))::<lambda(tree)> > /home/alecop01/toolchain/src/gcc/gcc/gimple-match-head.cc:1028 0x17255c4 gimple_simplify(gimple*, gimple_match_op*, gimple**, tree_node* (*)(tree_node*), tree_node* (*)(tree_node*)) /home/alecop01/toolchain/src/gcc/gcc/gimple-match-head.cc:1103 0xb239b6 gimple_fold_stmt_to_constant_1(gimple*, tree_node* (*)(tree_node*), tree_node* (*)(tree_node*)) /home/alecop01/toolchain/src/gcc/gcc/gimple-fold.cc:7441 0x113d196 visit_stmt /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-sccvn.cc:6134 0x113dcee process_bb /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-sccvn.cc:7844 0x1140b4d do_rpo_vn_1 /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-sccvn.cc:8443 0x114127c do_rpo_vn(function*, edge_def*, bitmap_head*, bool, bool, vn_lookup_kind) /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-sccvn.cc:8545 0x123c0ce execute /home/alecop01/toolchain/src/gcc/gcc/tree-vectorizer.cc:1388 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2023-01-06 10:38 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-06 10:38 acoplan at gcc dot gnu.org [this message] 2023-01-06 11:53 ` [Bug tree-optimization/108314] [13 Regression] Segfault in gimple-match-head.cc:do_valueize when vectorizing for SVE since r13-707-g68e0063397ba82 marxin at gcc dot gnu.org 2023-01-10 7:09 ` rguenth at gcc dot gnu.org 2023-01-10 9:40 ` rguenth at gcc dot gnu.org 2023-01-10 10:45 ` rguenth at gcc dot gnu.org 2023-01-10 10:46 ` rguenth at gcc dot gnu.org 2023-01-10 12:08 ` cvs-commit at gcc dot gnu.org 2023-01-10 12:09 ` 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-108314-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).