public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pan2.li at intel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/109617] New: RISC-V: ICE for vlmul_ext_v intrinsic API Date: Tue, 25 Apr 2023 02:06:20 +0000 [thread overview] Message-ID: <bug-109617-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109617 Bug ID: 109617 Summary: RISC-V: ICE for vlmul_ext_v intrinsic API Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pan2.li at intel dot com Target Milestone: --- Given we have the bellow sample code. #include <riscv_vector.h> vint16m8_t test_vlmul_ext_v_i16mf4_i16m8(vint16mf4_t op1) { return __riscv_vlmul_ext_v_i16mf4_i16m8(op1); } It will have ICE when building with this option "riscv64-unknown-elf-gcc -march=rv64gcv -O3 test.c -c -S -o -". during RTL pass: expand test.c: In function 'test_vlmul_ext_v_i16mf4_i16m8': test.c:7:10: internal compiler error: in code_for_vlmul_extx32, at ./insn-opinit.h:572 7 | return __riscv_vlmul_ext_v_i16mf4_i16m8(op1); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 0x1c07559 code_for_vlmul_extx32(machine_mode) ./insn-opinit.h:572 0x1c0b14e riscv_vector::vlmul_ext::expand(riscv_vector::function_expander&) const /home/pli/repos/toolchains/gcc/reference/riscv-gnu-toolchain/gcc/__BUILD_RISC-V/../gcc/config/riscv/riscv-vector-builtins-bases.cc:1522 0x1c03b2d riscv_vector::expand_builtin(unsigned int, tree_node*, rtx_def*) /home/pli/repos/toolchains/gcc/reference/riscv-gnu-toolchain/gcc/__BUILD_RISC-V/../gcc/config/riscv/riscv-vector-builtins.cc:3501 0x1bd8463 riscv_expand_builtin(tree_node*, rtx_def*, rtx_def*, machine_mode, int) /home/pli/repos/toolchains/gcc/reference/riscv-gnu-toolchain/gcc/__BUILD_RISC-V/../gcc/config/riscv/riscv-builtins.cc:379 0xe2951d expand_builtin(tree_node*, rtx_def*, rtx_def*, machine_mode, int) /home/pli/repos/toolchains/gcc/reference/riscv-gnu-toolchain/gcc/__BUILD_RISC-V/../gcc/builtins.cc:7341 0x103cb67 expand_expr_real_1(tree_node*, rtx_def*, machine_mode, expand_modifier, rtx_def**, bool) /home/pli/repos/toolchains/gcc/reference/riscv-gnu-toolchain/gcc/__BUILD_RISC-V/../gcc/expr.cc:11864 0x102e744 expand_expr_real(tree_node*, rtx_def*, machine_mode, expand_modifier, rtx_def**, bool) /home/pli/repos/toolchains/gcc/reference/riscv-gnu-toolchain/gcc/__BUILD_RISC-V/../gcc/expr.cc:8999 0x1022e43 store_expr(tree_node*, rtx_def*, int, bool, bool) /home/pli/repos/toolchains/gcc/reference/riscv-gnu-toolchain/gcc/__BUILD_RISC-V/../gcc/expr.cc:6330 0x10213c1 expand_assignment(tree_node*, tree_node*, bool) /home/pli/repos/toolchains/gcc/reference/riscv-gnu-toolchain/gcc/__BUILD_RISC-V/../gcc/expr.cc:6048 0xe6cab9 expand_call_stmt /home/pli/repos/toolchains/gcc/reference/riscv-gnu-toolchain/gcc/__BUILD_RISC-V/../gcc/cfgexpand.cc:2829 0xe70886 expand_gimple_stmt_1 /home/pli/repos/toolchains/gcc/reference/riscv-gnu-toolchain/gcc/__BUILD_RISC-V/../gcc/cfgexpand.cc:3880 0xe70f7a expand_gimple_stmt /home/pli/repos/toolchains/gcc/reference/riscv-gnu-toolchain/gcc/__BUILD_RISC-V/../gcc/cfgexpand.cc:4044 0xe79c1a expand_gimple_basic_block /home/pli/repos/toolchains/gcc/reference/riscv-gnu-toolchain/gcc/__BUILD_RISC-V/../gcc/cfgexpand.cc:6106 0xe7c17c execute /home/pli/repos/toolchains/gcc/reference/riscv-gnu-toolchain/gcc/__BUILD_RISC-V/../gcc/cfgexpand.cc:6841
next reply other threads:[~2023-04-25 2:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-25 2:06 pan2.li at intel dot com [this message] 2023-05-02 15:35 ` [Bug target/109617] " cvs-commit at gcc dot gnu.org 2023-05-02 15:37 ` kito 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-109617-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).