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/109535] [13/14] internal compiler error: in finalize_new_accesses, at rtl-ssa/changes.cc:471
Date: Thu, 20 Apr 2023 13:21:41 +0000	[thread overview]
Message-ID: <bug-109535-4-LvWI0hmjGl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109535-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kito Cheng <kito@gcc.gnu.org>:

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

commit r14-113-ga2d12abedc89a9439fd6aadc38730fdadca0684f
Author: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
Date:   Wed Apr 19 18:41:51 2023 +0800

    RISC-V: Fix wrong check of register occurrences [PR109535]

    count_occurrences will conly count same RTX (same code and same mode),
    but what we want to track is the occurrence of a register, a register
    might appeared in the insn with different mode or contain in SUBREG.

    Testcase coming from Kito.

    gcc/ChangeLog:

            PR target/109535
            * config/riscv/riscv-vsetvl.cc (count_regno_occurrences): New
function.
            (pass_vsetvl::cleanup_insns): Fix bug.

    gcc/testsuite/ChangeLog:

            PR target/109535
            * g++.target/riscv/rvv/base/pr109535.C: New test.
            * gcc.target/riscv/rvv/base/pr109535.c: New test.

    Signed-off-by: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
    Co-authored-by: kito-cheng <kito.cheng@sifive.com>

  parent reply	other threads:[~2023-04-20 13:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17  8:19 [Bug tree-optimization/109535] New: " malat at debian dot org
2023-04-17  8:23 ` [Bug target/109535] " malat at debian dot org
2023-04-17  8:49 ` rsandifo at gcc dot gnu.org
2023-04-17  9:19 ` juzhe.zhong at rivai dot ai
2023-04-17  9:26 ` juzhe.zhong at rivai dot ai
2023-04-17 10:00 ` kito at gcc dot gnu.org
2023-04-17 14:04 ` pan2.li at intel dot com
2023-04-17 14:54 ` kito at gcc dot gnu.org
2023-04-17 15:05 ` juzhe.zhong at rivai dot ai
2023-04-17 15:13 ` rsandifo at gcc dot gnu.org
2023-04-18  2:05 ` juzhe.zhong at rivai dot ai
2023-04-20 12:30 ` [Bug target/109535] [13/14] " kito at gcc dot gnu.org
2023-04-20 13:21 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-20 14:30 ` juzhe.zhong at rivai dot ai
2023-04-20 15:02 ` malat at debian dot org
2023-04-20 22:44 ` juzhe.zhong at rivai dot ai
2023-04-21  1:46 ` juzhe.zhong at rivai dot ai
2023-05-04  3:22 ` [Bug target/109535] [13 regression] " cvs-commit at gcc dot gnu.org
2023-05-04  3:23 ` 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-109535-4-LvWI0hmjGl@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).