public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114264] RISC-V: ICE in riscv-vector-costs.cc of gcc master branch
Date: Fri, 08 Mar 2024 02:43:17 +0000	[thread overview]
Message-ID: <bug-114264-4-WexVQhZUbN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114264-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114264

--- Comment #1 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Demin Han <deminhan@gcc.gnu.org>:

https://gcc.gnu.org/g:42187c6968af9907de1f9b7563d87de739857684

commit r14-9380-g42187c6968af9907de1f9b7563d87de739857684
Author: demin.han <demin.han@starfivetech.com>
Date:   Wed Mar 6 17:34:34 2024 +0800

    RISC-V: Fix ICE in riscv vector costs

    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);
      }
    }

    One biggest_mode update missed in one branch and trigger assertion fail.
    gcc_assert (biggest_size >= mode_size);

    Tested On RV64 and no regression.

            PR target/114264

    gcc/ChangeLog:

            * config/riscv/riscv-vector-costs.cc: Fix ICE

    gcc/testsuite/ChangeLog:

            * gcc.dg/vect/costmodel/riscv/rvv/pr114264.c: New test.

    Signed-off-by: demin.han <demin.han@starfivetech.com>

  reply	other threads:[~2024-03-08  2:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07  8:01 [Bug target/114264] New: " deminhan at gcc dot gnu.org
2024-03-08  2:43 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-09  7:36 ` [Bug target/114264] " 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-WexVQhZUbN@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: link
Be 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).