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 middle-end/113494] New: [14 Regression] ICE (segfault) in slpeel_tree_duplicate_loop_to_edge_cfg since r14-8206-g0f38666680d6ad0e Date: Thu, 18 Jan 2024 22:27:34 +0000 [thread overview] Message-ID: <bug-113494-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113494 Bug ID: 113494 Summary: [14 Regression] ICE (segfault) in slpeel_tree_duplicate_loop_to_edge_cfg since r14-8206-g0f38666680d6ad0e Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: acoplan at gcc dot gnu.org Target Milestone: --- The following fails on aarch64: ./xgcc -B . -c ~/toolchain/src/gcc/gcc/testsuite/gcc.c-torture/execute/20150611-1.c -S -o /dev/null -O3 during GIMPLE pass: vect /home/alecop01/toolchain/src/gcc/gcc/testsuite/gcc.c-torture/execute/20150611-1.c: In function ‘main’: /home/alecop01/toolchain/src/gcc/gcc/testsuite/gcc.c-torture/execute/20150611-1.c:5:1: internal compiler error: Segmentation fault 5 | main () | ^~~~ 0x30bdd30 crash_signal /home/alecop01/toolchain/src/gcc/gcc/toplev.cc:317 0x7f38d1b6708f ??? /build/glibc-wuryBv/glibc-2.31/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0 0x26e6cf6 gimple_phi_result(gphi const*) /home/alecop01/toolchain/src/gcc/gcc/gimple.h:4608 0x34b7f10 slpeel_tree_duplicate_loop_to_edge_cfg(loop*, edge_def*, loop*, edge_def*, edge_def*, edge_def**, bool, vec<basic_block_def*, va_heap, vl_ptr>*) /home/alecop01/toolchain/src/gcc/gcc/tree-vect-loop-manip.cc:1751 0x34bceea vect_do_peeling(_loop_vec_info*, tree_node*, tree_node*, tree_node**, tree_node**, tree_node**, int, bool, bool, tree_node**) /home/alecop01/toolchain/src/gcc/gcc/tree-vect-loop-manip.cc:3342 0x34a85f3 vect_transform_loop(_loop_vec_info*, gimple*) /home/alecop01/toolchain/src/gcc/gcc/tree-vect-loop.cc:11929 0x34fdcda vect_transform_loops /home/alecop01/toolchain/src/gcc/gcc/tree-vectorizer.cc:1006 0x34fe445 try_vectorize_loop_1 /home/alecop01/toolchain/src/gcc/gcc/tree-vectorizer.cc:1152 0x34fe57e try_vectorize_loop /home/alecop01/toolchain/src/gcc/gcc/tree-vectorizer.cc:1182 0x34fe844 execute /home/alecop01/toolchain/src/gcc/gcc/tree-vectorizer.cc:1298 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:[~2024-01-18 22:27 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-18 22:27 acoplan at gcc dot gnu.org [this message] 2024-01-18 22:35 ` [Bug middle-end/113494] " pinskia at gcc dot gnu.org 2024-01-18 22:39 ` pinskia at gcc dot gnu.org 2024-01-19 9:17 ` rguenth at gcc dot gnu.org 2024-01-19 9:43 ` cvs-commit at gcc dot gnu.org 2024-01-19 9:48 ` 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-113494-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).