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/109773] New: RISC-V: ICE when build RVV Intrinisc Date: Mon, 08 May 2023 14:52:53 +0000 [thread overview] Message-ID: <bug-109773-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109773 Bug ID: 109773 Summary: RISC-V: ICE when build RVV Intrinisc 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: --- There will be one ICE when trying to build the below code with the option '-march=rv64gcv -O3 -fno-schedule-insns -c -S test.c -o -'. #include "riscv_vector.h" void f4 (int32_t * a, int32_t * b, int n) { if (n <= 0) return; int i = n; size_t vl = __riscv_vsetvl_e8mf4 (i); for (; i >= 0; i--) { vint32m1_t v = __riscv_vle32_v_i32m1 (a + i, vl); v = __riscv_vle32_v_i32m1_tu (v, a + i + 100, vl); __riscv_vse32_v_i32m1 (b + i, v, vl); if (i >= vl) continue; if (i == 0) return; vl = __riscv_vsetvl_e8mf4 (vl); } } The output of compiling. > riscv64-unknown-linux-gnu-gcc -march=rv64gcv -O3 -fno-schedule-insns -c -S test.c -o - .file "test.c" .option nopic .attribute arch, "rv64i2p1_m2p0_a2p1_f2p2_d2p2_c2p0_v1p0_zicsr2p0_zifencei2p0_zve32f1p0_zve32x1p0_zve64d1p0_zve64f1p0_zve64x1p0_zvl128b1p0_zvl32b1p0_zvl64b1p0" .attribute unaligned_access, 0 .attribute stack_align, 16 .text riscv64-unknown-linux-gnu-gcc: internal compiler error: Segmentation fault signal terminated program cc1 Please submit a full bug report, with preprocessed source (by using -freport-bug). See <https://gcc.gnu.org/bugs/> for instructions. > riscv-gnu-toolchain@<22:46:54 一 5月 08>[4]*1*[3s]"~/bin/gnu-rv64-linux-13/bin/riscv64-unknown-linux-gnu-gcc -march=rv64gcv -O3 -fno-schedule-insns -c -S test.c -o -" >> ~/bin/gnu-rv64-linux-13/bin/riscv64-unknown-linux-gnu-gcc --version riscv64-unknown-linux-gnu-gcc (g1c9c53f0256) 13.1.1 20230508 Copyright (C) 2023 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
next reply other threads:[~2023-05-08 14:52 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-08 14:52 pan2.li at intel dot com [this message] 2023-05-08 14:54 ` [Bug c/109773] RISC-V: ICE when build RVV Intrinsic in Both GCC 13 && GCC 14 juzhe.zhong at rivai dot ai 2023-05-10 8:22 ` [Bug target/109773] " cvs-commit at gcc dot gnu.org 2023-09-07 10:28 ` 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-109773-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).