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/109104] [13 Regression] ICE: in gen_reg_rtx, at emit-rtl.cc:1171 with -fzero-call-used-regs=all -march=rv64gv
Date: Tue, 11 Apr 2023 14:09:30 +0000	[thread overview]
Message-ID: <bug-109104-4-S9Qbi8EnXF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109104-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 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:40fc8e3d4f600d89e6b065d6f12db7a816269c8f

commit r13-7138-g40fc8e3d4f600d89e6b065d6f12db7a816269c8f
Author: Yanzhang Wang <yanzhang.wang@intel.com>
Date:   Tue Apr 11 19:37:48 2023 +0800

    RISC-V: Fix regression of -fzero-call-used-regs=all [PR109104]

    This patch registers a riscv specific function to
    TARGET_ZERO_CALL_USED_REGS instead of default in targhooks.cc. It will
    clean gpr and vector relevant registers.

    gcc/ChangeLog:

            PR target/109104
            * config/riscv/riscv-protos.h (emit_hard_vlmax_vsetvl): New.
            * config/riscv/riscv-v.cc (emit_hard_vlmax_vsetvl): New.
            (emit_vlmax_vsetvl): Use emit_hard_vlmax_vsetvl.
            * config/riscv/riscv.cc (vector_zero_call_used_regs): New.
            (riscv_zero_call_used_regs): New.
            (TARGET_ZERO_CALL_USED_REGS): New.

    gcc/testsuite/ChangeLog:

            PR target/109104
            * gcc.target/riscv/zero-scratch-regs-1.c: New test.
            * gcc.target/riscv/zero-scratch-regs-2.c: New test.
            * gcc.target/riscv/zero-scratch-regs-3.c: New test.

    Signed-off-by: Yanzhang Wang <yanzhang.wang@intel.com>
    Co-authored-by: Pan Li <pan2.li@intel.com>
    Co-authored-by: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
    Co-authored-by: Kito Cheng <kito.cheng@sifive.com>

  parent reply	other threads:[~2023-04-11 14:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 10:53 [Bug target/109104] New: " zsojka at seznam dot cz
2023-03-11 16:31 ` [Bug target/109104] " pinskia at gcc dot gnu.org
2023-03-14  8:43 ` roger at nextmovesoftware dot com
2023-03-14  8:49 ` juzhe.zhong at rivai dot ai
2023-03-30 12:06 ` marxin at gcc dot gnu.org
2023-03-30 13:41 ` kito at gcc dot gnu.org
2023-03-31 14:44 ` yanzhang.wang at intel dot com
2023-04-08 14:34 ` law at gcc dot gnu.org
2023-04-11 14:09 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-17 13:28 ` [Bug target/109104] [13/14 " 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-109104-4-S9Qbi8EnXF@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).