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/97104] New: [11 Regression] aarch64, SVE: ICE in vect_get_loop_mask since r11-3070-g783dc66f9cc Date: Fri, 18 Sep 2020 11:19:29 +0000 [thread overview] Message-ID: <bug-97104-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97104 Bug ID: 97104 Summary: [11 Regression] aarch64, SVE: ICE in vect_get_loop_mask since r11-3070-g783dc66f9cc Product: gcc Version: 11.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: --- For the following testcase: int a, b, c, d; short e; void f() { unsigned g; for (; d; d++) { g = c == 0 ? 1 : b / c; e = a ? g : a; } } AArch64 GCC ICEs at -O1 or -O2 with -ftree-vectorize -march=armv8.2-a+sve since r11-3070-g783dc66f9ccb0019c3dad2701bb9110286758d70: commit 783dc66f9ccb0019c3dad2701bb9110286758d70 (HEAD) Author: Richard Biener <rguenther@suse.de> Date: Wed Sep 9 09:36:46 2020 enable live condition vectorization To reproduce: $ aarch64-none-elf-gcc -O2 -ftree-vectorize -march=armv8.2-a+sve test.c during GIMPLE pass: vect test.c: In function 'f': test.c:3:6: internal compiler error: in operator[], at vec.h:880 3 | void f() { | ^ 0x10637d9 vec<rgroup_controls, va_heap, vl_embed>::operator[](unsigned int) /home/alecop01/toolchain/src/gcc/gcc/vec.h:880 0x10637d9 vec<rgroup_controls, va_heap, vl_ptr>::operator[](unsigned int) /home/alecop01/toolchain/src/gcc/gcc/vec.h:1451 0x10637d9 vect_get_loop_mask(gimple_stmt_iterator*, auto_vec<rgroup_controls, 0ul>*, unsigned int, tree_node*, unsigned int) /home/alecop01/toolchain/src/gcc/gcc/tree-vect-loop.c:8487 0x1044e00 vectorizable_condition /home/alecop01/toolchain/src/gcc/gcc/tree-vect-stmts.c:10216 0x105a73e vect_transform_stmt(vec_info*, _stmt_vec_info*, gimple_stmt_iterator*, _slp_tree*, _slp_instance*) /home/alecop01/toolchain/src/gcc/gcc/tree-vect-stmts.c:10859 0x1061099 vect_transform_loop_stmt /home/alecop01/toolchain/src/gcc/gcc/tree-vect-loop.c:8700 0x107db5d vect_transform_loop(_loop_vec_info*, gimple*) /home/alecop01/toolchain/src/gcc/gcc/tree-vect-loop.c:9134 0x10a3c34 try_vectorize_loop_1 /home/alecop01/toolchain/src/gcc/gcc/tree-vectorizer.c:1094 0x10a43b6 try_vectorize_loop /home/alecop01/toolchain/src/gcc/gcc/tree-vectorizer.c:1151 0x10a46f0 vectorize_loops() /home/alecop01/toolchain/src/gcc/gcc/tree-vectorizer.c:1230 0xf392f7 execute /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-loop.c:414 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 reply other threads:[~2020-09-18 11:19 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-18 11:19 acoplan at gcc dot gnu.org [this message] 2020-09-18 11:20 ` [Bug tree-optimization/97104] " acoplan at gcc dot gnu.org 2020-09-18 12:04 ` rguenth at gcc dot gnu.org 2020-10-16 12:09 ` rguenth at gcc dot gnu.org 2020-11-05 9:49 ` acoplan at gcc dot gnu.org 2020-12-10 17:00 ` akrl at gcc dot gnu.org 2021-01-14 16:13 ` acoplan at gcc dot gnu.org 2021-03-09 14:24 ` rguenth at gcc dot gnu.org 2021-03-09 14:25 ` acoplan at gcc dot gnu.org 2021-03-09 14:57 ` acoplan 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-97104-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).