public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113766] New: ICE: in generate_insn, at config/riscv/riscv-vector-builtins.cc:4186 with (invalid?) __riscv_vfredosum_tu() Date: Mon, 05 Feb 2024 11:57:23 +0000 [thread overview] Message-ID: <bug-113766-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113766 Bug ID: 113766 Summary: ICE: in generate_insn, at config/riscv/riscv-vector-builtins.cc:4186 with (invalid?) __riscv_vfredosum_tu() Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz Target Milestone: --- Host: x86_64-pc-linux-gnu Target: riscv64-unknown-linux-gnu Created attachment 57323 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57323&action=edit reduced testcase Compiler output: $ riscv64-unknown-linux-gnu-gcc -march=rv64gv testcase.c during RTL pass: expand testcase.c: In function 'foo': testcase.c:6:3: internal compiler error: in generate_insn, at config/riscv/riscv-vector-builtins.cc:4186 6 | __riscv_vfredosum_tu(); | ^~~~~~~~~~~~~~~~~~~~~~ 0xb9bd49 riscv_vector::function_expander::generate_insn(insn_code) /repo/gcc-trunk/gcc/config/riscv/riscv-vector-builtins.cc:4186 0xb9bd49 riscv_vector::function_expander::generate_insn(insn_code) /repo/gcc-trunk/gcc/config/riscv/riscv-vector-builtins.cc:4184 0x1bcd50d riscv_vector::function_expander::expand() /repo/gcc-trunk/gcc/config/riscv/riscv-vector-builtins.h:582 0x1bcd50d riscv_vector::expand_builtin(unsigned int, tree_node*, rtx_def*) /repo/gcc-trunk/gcc/config/riscv/riscv-vector-builtins.cc:4589 0x12ca5e3 expand_expr_real_1(tree_node*, rtx_def*, machine_mode, expand_modifier, rtx_def**, bool) /repo/gcc-trunk/gcc/expr.cc:12350 0x1187df8 expand_expr(tree_node*, rtx_def*, machine_mode, expand_modifier) /repo/gcc-trunk/gcc/expr.h:316 0x1187df8 expand_call_stmt /repo/gcc-trunk/gcc/cfgexpand.cc:2864 0x1187df8 expand_gimple_stmt_1 /repo/gcc-trunk/gcc/cfgexpand.cc:3926 0x1187df8 expand_gimple_stmt /repo/gcc-trunk/gcc/cfgexpand.cc:4071 0x118e45e expand_gimple_basic_block /repo/gcc-trunk/gcc/cfgexpand.cc:6127 0x1190067 execute /repo/gcc-trunk/gcc/cfgexpand.cc:6866 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. $ riscv64-unknown-linux-gnu-gcc -v Using built-in specs. COLLECT_GCC=/repo/gcc-trunk/binary-latest-riscv64/bin/riscv64-unknown-linux-gnu-gcc COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r14-8795-20240204180638-g91e09b3a7e9-checking-yes-rtl-df-extra-riscv64/bin/../libexec/gcc/riscv64-unknown-linux-gnu/14.0.1/lto-wrapper Target: riscv64-unknown-linux-gnu Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++ --enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra --with-cloog --with-ppl --with-isl --with-isa-spec=2.2 --with-sysroot=/usr/riscv64-unknown-linux-gnu --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=riscv64-unknown-linux-gnu --with-ld=/usr/bin/riscv64-unknown-linux-gnu-ld --with-as=/usr/bin/riscv64-unknown-linux-gnu-as --disable-multilib --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r14-8795-20240204180638-g91e09b3a7e9-checking-yes-rtl-df-extra-riscv64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 14.0.1 20240205 (experimental) (GCC)
next reply other threads:[~2024-02-05 11:57 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-05 11:57 zsojka at seznam dot cz [this message] 2024-02-06 0:44 ` [Bug target/113766] " pan2.li at intel dot com 2024-02-07 1:19 ` cvs-commit at gcc dot gnu.org 2024-02-08 6:52 ` cvs-commit 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-113766-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).