On 12/20/23 20:30, Wang Pengcheng wrote:
Yeah, I just found it when I tried to understand the original fusion
implementation commit. :-)
Ah. If you have any questions, don't hesitate to reach out. While I
didn't do the original implementation (that was Philipp T. and his
team), the basic
On 2023/12/21 1:08, Jeff Law wrote:
>
>
> On 12/20/23 01:39, Wang Pengcheng wrote:
>> From: wangpc
>>
>> The condition is RISCV_FUSE_ZEXTH, which is a mistake.
>>
>> gcc/ChangeLog:
>>
>> * config/riscv/riscv.cc (riscv_macro_fusion_pair_p): Fix condition.
> Thanks! As soon as this patch finishes re
code.
Thanks again!
jeffcommit eef65d60a8bb2e9328fd9d2b6cd869618be4f08e
Author: Wang Pengcheng
Date: Wed Dec 20 10:32:59 2023 -0700
[PATCH] RISC-V: Fix RISCV_FUSE_ZEXTWS fusion condition
The condition is RISCV_FUSE_ZEXTH, which is a mistake.
gcc/Chan
On 12/20/23 01:39, Wang Pengcheng wrote:
From: wangpc
The condition is RISCV_FUSE_ZEXTH, which is a mistake.
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_macro_fusion_pair_p): Fix condition.
Thanks! As soon as this patch finishes regression testing I'll push it
to the trunk.
I'm curiou
From: wangpc
The condition is RISCV_FUSE_ZEXTH, which is a mistake.
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_macro_fusion_pair_p): Fix condition.
---
gcc/config/riscv/riscv.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/config/riscv/riscv.cc b/gcc/config/riscv/ris