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 middle-end/111548] RISC-V Vector: ICE in validate_change_or_fail (vsetvl pass)
Date: Mon, 25 Sep 2023 06:12:13 +0000	[thread overview]
Message-ID: <bug-111548-4-mtdjzv2Cac@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111548-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Pan Li <panli@gcc.gnu.org>:

https://gcc.gnu.org/g:9d5f20fc4a6b3254d2d379309193da4be2747987

commit r14-4248-g9d5f20fc4a6b3254d2d379309193da4be2747987
Author: Juzhe-Zhong <juzhe.zhong@rivai.ai>
Date:   Sun Sep 24 11:17:01 2023 +0800

    RISC-V: Fix AVL/VL bug of VSETVL PASS[PR111548]

    This patch fixes that AVL/VL reg incorrect fetch in VSETVL PASS.

    C/C++ regression passed.

    But gfortran didn't run yet. I am still finding a way to run it.

    Will commit it when I pass the fortran regression.

            PR target/111548

    gcc/ChangeLog:

            * config/riscv/riscv-vsetvl.cc (earliest_pred_can_be_fused_p):
Bugfix

    gcc/testsuite/ChangeLog:

            * gcc.target/riscv/rvv/autovec/pr111548.c: New test.

  reply	other threads:[~2023-09-25  6:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23 13:16 [Bug middle-end/111548] New: " jeremy.bennett at embecosm dot com
2023-09-25  6:12 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-03  8:28 ` [Bug middle-end/111548] " jeremy.bennett at embecosm dot com

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-111548-4-mtdjzv2Cac@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).