> So I guess you should change `fscsr` to `fscsr%i0` instead of dropping
> K from the constraint list?
>
Sorry, you are right. I thought you were talking about fsflags,
but I didn't notice it was fscsr. I'll correct it right away.
> On Wed, Jul 26, 2023 at 11:42 AM juzhe.zh...@rivai.ai
> wrote:
only).
Thanks.
juzhe.zh...@rivai.ai
From: Kito Cheng
Date: 2023-07-26 11:45
To: juzhe.zh...@rivai.ai
CC: jinma; gcc-patches; jeffreyalaw; palmer; richard.sandiford;
philipp.tomsich; christoph.muellner; Robin Dapp; jinma.contrib
Subject: Re: Re: [PATCH v3] RISC-V: Fixbug for fsflags instruct
So I guess you should change `fscsr` to `fscsr%i0` instead of dropping
K from the constraint list?
On Wed, Jul 26, 2023 at 11:42 AM juzhe.zh...@rivai.ai
wrote:
>
> I don't understand:
> (define_insn "riscv_fscsr"
> - [(unspec_volatile [(match_operand:SI 0 "csr_operand" "rK")] UNSPECV_FSCSR)]
>
I don't understand:
(define_insn "riscv_fscsr"
- [(unspec_volatile [(match_operand:SI 0 "csr_operand" "rK")] UNSPECV_FSCSR)]
+ [(unspec_volatile [(match_operand:SI 0 "csr_operand" "r")] UNSPECV_FSCSR)]
"TARGET_HARD_FLOAT || TARGET_ZFINX"
"fscsr\t%0")
This pattern never allows immediate in
