public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "deminhan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114264] New: RISC-V: ICE in riscv-vector-costs.cc of gcc master branch Date: Thu, 07 Mar 2024 08:01:41 +0000 [thread overview] Message-ID: <bug-114264-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114264 Bug ID: 114264 Summary: RISC-V: ICE in riscv-vector-costs.cc of gcc master branch Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: deminhan at gcc dot gnu.org Target Milestone: --- The following code can result in ICE: -march=rv64gcv --param riscv-autovec-lmul=dynamic -O3 char *jpeg_difference7_input_buf; void jpeg_difference7(int *diff_buf) { unsigned width; int samp, Rb; while (--width) { Rb = samp = *jpeg_difference7_input_buf; *diff_buf++ = -(int)(samp + (long)Rb >> 1); } } during GIMPLE pass: vect testcase.i: In function 'jpeg_difference7': testcase.i:2:6: internal compiler error: in compute_nregs_for_mode, at config/riscv/riscv-vector-costs.cc:453 2 | void jpeg_difference7(int *diff_buf) { | ^~~~~~~~~~~~~~~~ 0xb2a30f compute_nregs_for_mode ../../../gcc/gcc/config/riscv/riscv-vector-costs.cc:453 0x17b19e6 max_number_of_live_regs ../../../gcc/gcc/config/riscv/riscv-vector-costs.cc:492 0x17b57a5 has_unexpected_spills_p ../../../gcc/gcc/config/riscv/riscv-vector-costs.cc:834
next reply other threads:[~2024-03-07 8:01 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-07 8:01 deminhan at gcc dot gnu.org [this message] 2024-03-08 2:43 ` [Bug target/114264] " cvs-commit at gcc dot gnu.org 2024-03-09 7:36 ` law 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-114264-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).