Re: Re: [PATCH] RISC-V: Add v_uimm_operand

2023-05-11 Thread 钟居哲
LGTM juzhe.zh...@rivai.ai From: Palmer Dabbelt Date: 2023-05-12 06:31 To: juzhe.zhong CC: gcc-patches; jeffreyalaw Subject: Re: [PATCH] RISC-V: Add v_uimm_operand On Thu, 11 May 2023 15:00:48 PDT (-0700), juzhe.zh...@rivai.ai wrote: >>> ;; V has 32-bit unsigned immediates. Thi

Re: [PATCH] RISC-V: Add v_uimm_operand

2023-05-11 Thread Palmer Dabbelt
On Thu, 11 May 2023 15:00:48 PDT (-0700), juzhe.zh...@rivai.ai wrote: ;; V has 32-bit unsigned immediates. This happens to be the same constraint asIt should be 5-bit unsigned immediates>> ; the csr_operand, but it's not CSR related. (define_predicate "v_uimm_operand" (match_operand 0

[PATCH] RISC-V: Add v_uimm_operand

2023-05-11 Thread 钟居哲
>> ;; V has 32-bit unsigned immediates. This happens to be the same >> constraint asIt should be 5-bit unsigned immediates>> ; the csr_operand, >> but it's not CSR related. >> (define_predicate "v_uimm_operand" >> (match_operand 0 "csr_operand")) To make name consistent, it should be

[PATCH] RISC-V: Add v_uimm_operand

2023-05-11 Thread Palmer Dabbelt
The vector shift immediates happen to have the same constraints as some of the CSR-related operands, but it's a different usage. This adds a name for them, so I don't get confused again next time. gcc/ChangeLog: * config/riscv/autovec.md (shifts): Use v_uimm_operand. *