public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Pan Li <panli@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-10117] RISC-V: Add early clobber to the dest of vwsll
Date: Thu, 25 Apr 2024 06:36:47 +0000 (GMT)	[thread overview]
Message-ID: <20240425063647.E6008384640E@sourceware.org> (raw)

https://gcc.gnu.org/g:10ad46bc191f8aa90b0d7b00963bfd52c6d7b09c

commit r14-10117-g10ad46bc191f8aa90b0d7b00963bfd52c6d7b09c
Author: Pan Li <pan2.li@intel.com>
Date:   Thu Apr 25 08:55:08 2024 +0800

    RISC-V: Add early clobber to the dest of vwsll
    
    We missed the existing early clobber for the dest operand of vwsll
    pattern when resolve the conflict of revert register overlap.  Thus
    add it back to the pattern.  Unfortunately, we have no test to cover
    this part and will improve this after GCC-15 open.
    
    The below tests are passed for this patch:
    * The rv64gcv fully regression test with isl build.
    
    gcc/ChangeLog:
    
            * config/riscv/vector-crypto.md: Add early clobber to the
            dest operand of vwsll.
    
    Signed-off-by: Pan Li <pan2.li@intel.com>

Diff:
---
 gcc/config/riscv/vector-crypto.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/config/riscv/vector-crypto.md b/gcc/config/riscv/vector-crypto.md
index 8a4888a7653..e474ddf5da7 100755
--- a/gcc/config/riscv/vector-crypto.md
+++ b/gcc/config/riscv/vector-crypto.md
@@ -303,7 +303,7 @@
    (set_attr "mode" "<V_DOUBLE_TRUNC>")])
 
 (define_insn "@pred_vwsll<mode>_scalar"
-  [(set (match_operand:VWEXTI 0 "register_operand"              "=vr,     vr")
+  [(set (match_operand:VWEXTI 0 "register_operand"              "=&vr,    &vr")
      (if_then_else:VWEXTI
        (unspec:<VM>
          [(match_operand:<VM> 1 "vector_mask_operand"           "vmWc1, vmWc1")

                 reply	other threads:[~2024-04-25  6:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240425063647.E6008384640E@sourceware.org \
    --to=panli@gcc.gnu.org \
    --cc=gcc-cvs@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).