public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: Kito.cheng <kito.cheng@sifive.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	 kito.cheng <kito.cheng@gmail.com>,
	 jeffreyalaw <jeffreyalaw@gmail.com>,
	 "Robin Dapp" <rdapp.gcc@gmail.com>
Subject: Re: Re: [PATCH V3] RISC-V: Enable basic VLS modes support
Date: Thu, 27 Jul 2023 17:50:13 +0800	[thread overview]
Message-ID: <00ACAA2AAB2B9A73+2023072717501238592275@rivai.ai> (raw)
In-Reply-To: <CALLt3TjG+Lm5nfP331-LvJKdmm3ee4uoMb0h6jjPJ4xsOtQgSA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]

Hi, kito.
I tried to reject mem->mem in this pattern:
(define_insn_and_split "*mov<mode>"
  [(set (match_operand:VLS_AVL_IMM 0 "reg_or_mem_operand" "=vr, m, vr")
        (match_operand:VLS_AVL_IMM 1 "reg_or_mem_operand" "  m,vr, vr"))]
  "TARGET_VECTOR
   && (register_operand (operands[0], <MODE>mode)
       || register_operand (operands[1], <MODE>mode))"
  "@
   #
   #
   vmv%m1r.v\t%0,%1"
  "&& reload_completed
   && (!register_operand (operands[0], <MODE>mode)
       || !register_operand (operands[1], <MODE>mode))"
  [(const_int 0)]
  {
    bool ok_p = riscv_vector::legitimize_move (operands[0], operands[1]);
    gcc_assert (ok_p);
    DONE;
  }
)


It cause ICE in regression during "vregs" (Before RA).
[jzzhong@server1:/work/home/jzzhong/work/insn]$~/work/rvv-opensource/output/gcc-rv64/bin/riscv64-rivai-elf-gcc -march=rv64gc_zve32f -mabi=lp64d -O3 -S --param=riscv-autovec-preference=scalable -fdump-rtl-all auto.c
auto.c: In function 'foo0':
auto.c:15:1: error: unrecognizable insn:
   15 | }
      | ^
(insn 35 34 36 6 (set (mem:V8QI (reg/f:DI 154 [ _64 ]) [0 MEM <vector(8) signed char> [(int8_t *)_64]+0 S8 A64])
        (mem/u/c:V8QI (reg/f:DI 185) [0  S8 A64])) "auto.c":11:20 -1
     (nil))
during RTL pass: vregs
dump file: auto.c.259r.vregs


It seems that we need a placeholder pattern to hold mem->mem ?

Could you help me with that ?


juzhe.zhong@rivai.ai
 
From: Kito Cheng
Date: 2023-07-27 17:19
To: Juzhe-Zhong
CC: gcc-patches; kito.cheng; jeffreyalaw; rdapp.gcc
Subject: Re: [PATCH V3] RISC-V: Enable basic VLS modes support
Last minor thing :)
 
> +(define_insn_and_split "*mov<mode>"
> +  [(set (match_operand:VLS_AVL_IMM 0 "reg_or_mem_operand" "=vr, m, vr")
> +       (match_operand:VLS_AVL_IMM 1 "reg_or_mem_operand" "  m,vr, vr"))]
> +  "TARGET_VECTOR"
 
Reject (set (mem) (mem)) by adding the check:
 
TARGET_VECTOR
&& (register_operand (operands[0], <VLS_AVL_REG:MODE>mode)
    || register_operand (operands[1], <VLS_AVL_REG:MODE>mode))"
 

  reply	other threads:[~2023-07-27  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27  9:06 Juzhe-Zhong
2023-07-27  9:19 ` Kito Cheng
2023-07-27  9:50   ` juzhe.zhong [this message]
2023-07-27  9:57     ` Kito Cheng
2023-07-27 10:04       ` juzhe.zhong
2023-07-27 10:35       ` juzhe.zhong

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=00ACAA2AAB2B9A73+2023072717501238592275@rivai.ai \
    --to=juzhe.zhong@rivai.ai \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=kito.cheng@gmail.com \
    --cc=kito.cheng@sifive.com \
    --cc=rdapp.gcc@gmail.com \
    /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).