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/111234] RISC-V: ICE in vsetvl pass
Date: Thu, 31 Aug 2023 02:10:03 +0000	[thread overview]
Message-ID: <bug-111234-4-LEqNoBjMCp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111234-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Lehua Ding <lhtin@gcc.gnu.org>:

https://gcc.gnu.org/g:ac55f9710fe82a4ed8cb132f57303775ce60e5d1

commit r14-3583-gac55f9710fe82a4ed8cb132f57303775ce60e5d1
Author: Lehua Ding <lehua.ding@rivai.ai>
Date:   Wed Aug 30 17:48:00 2023 +0800

    RISC-V: Fix vsetvl pass ICE

    This patch fix pr111234 (a vsetvl pass ICE) when fuse a mask any
    vlmax vsetvl_vtype_change_only insn with a mu vsetvl insn.

            PR target/111234

    gcc/ChangeLog:

            * config/riscv/riscv-vsetvl.cc (gen_vsetvl_pat): Remove condition.

    gcc/testsuite/ChangeLog:

            * gcc.target/riscv/rvv/vsetvl/pr111234.c: New test.

  parent reply	other threads:[~2023-08-31  2:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30  9:35 [Bug target/111234] New: " lehua.ding at rivai dot ai
2023-08-30  9:38 ` [Bug target/111234] " lehua.ding at rivai dot ai
2023-08-31  2:10 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-20  3:56 ` cvs-commit at gcc dot gnu.org
2024-04-24  8:50 ` [Bug target/111234] [13] " kito at gcc dot gnu.org
2024-04-29 14:02 ` cvs-commit at gcc dot gnu.org
2024-04-29 14:02 ` 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-111234-4-LEqNoBjMCp@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).