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 target/108316] New: [13 Regression] ICE in maybe_gen_insn via expand_SCATTER_STORE when vectorizing for SVE Date: Fri, 06 Jan 2023 11:42:37 +0000 [thread overview] Message-ID: <bug-108316-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108316 Bug ID: 108316 Summary: [13 Regression] ICE in maybe_gen_insn via expand_SCATTER_STORE when vectorizing for SVE Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target 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.cc extern bool a[]; short i; void f(int b[][3][2]) { for (; i; i += 4) a[i] = b[0][i] != 0; } $ aarch64-none-elf-gcc -c t.cc -march=armv9-a -O2 -fvect-cost-model=unlimited during RTL pass: expand t.cc: In function 'void f(int (*)[3][2])': t.cc:3:6: internal compiler error: in maybe_gen_insn, at optabs.cc:8059 3 | void f(int b[][3][2]) { | ^ 0x105f613 maybe_gen_insn(insn_code, unsigned int, expand_operand*) /home/alecop01/toolchain/src/gcc/gcc/optabs.cc:8059 0x105f80e maybe_expand_insn(insn_code, unsigned int, expand_operand*) /home/alecop01/toolchain/src/gcc/gcc/optabs.cc:8105 0x105ed93 expand_insn(insn_code, unsigned int, expand_operand*) /home/alecop01/toolchain/src/gcc/gcc/optabs.cc:8136 0xead67a expand_scatter_store_optab_fn /home/alecop01/toolchain/src/gcc/gcc/internal-fn.cc:3430 0xead8dd expand_SCATTER_STORE /home/alecop01/toolchain/src/gcc/gcc/internal-fn.def:137 0xeaddd2 expand_internal_call(internal_fn, gcall*) /home/alecop01/toolchain/src/gcc/gcc/internal-fn.cc:4436 0xeaddec expand_internal_call(gcall*) /home/alecop01/toolchain/src/gcc/gcc/internal-fn.cc:4444 0xbffbdc expand_call_stmt /home/alecop01/toolchain/src/gcc/gcc/cfgexpand.cc:2737 0xbffbdc expand_gimple_stmt_1 /home/alecop01/toolchain/src/gcc/gcc/cfgexpand.cc:3880 0xbffbdc expand_gimple_stmt /home/alecop01/toolchain/src/gcc/gcc/cfgexpand.cc:4044 0xc0916f expand_gimple_basic_block /home/alecop01/toolchain/src/gcc/gcc/cfgexpand.cc:6096 0xc0a9b9 execute /home/alecop01/toolchain/src/gcc/gcc/cfgexpand.cc:6822 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 11:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-06 11:42 acoplan at gcc dot gnu.org [this message] 2023-01-06 12:18 ` [Bug target/108316] [13 Regression] ICE in maybe_gen_insn via expand_SCATTER_STORE when vectorizing for SVE since r13-2737-g4a773bf2f08656 marxin at gcc dot gnu.org 2023-01-10 7:09 ` rguenth at gcc dot gnu.org 2023-02-06 13:49 ` jakub at gcc dot gnu.org 2023-02-06 15:06 ` jakub at gcc dot gnu.org 2023-02-07 15:31 ` rsandifo at gcc dot gnu.org 2023-02-08 13:40 ` cvs-commit at gcc dot gnu.org 2023-02-11 15:00 ` [Bug target/108316] " jakub at gcc dot gnu.org 2023-04-26 6:57 ` rguenth at gcc dot gnu.org 2023-07-27 9:25 ` rguenth at gcc dot gnu.org 2024-05-21 9:13 ` jakub 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-108316-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).