Address comments:
https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628568.html
juzhe.zh...@rivai.ai
From: Kito Cheng
Date: 2023-08-28 16:58
To: Robin Dapp
CC: Juzhe-Zhong; gcc-patches; kito.cheng
Subject: Re: [PATCH] RISC-V: Disable user vsetvl fusion into EMPTY block
Is it possible to
What about that? I guess I don't really know how to determine if a
block is EMPTY?
diff --git a/gcc/config/riscv/riscv-vsetvl.cc b/gcc/config/riscv/riscv-vsetvl.cc
index 682f795c8e1..784ab184c72 100644
--- a/gcc/config/riscv/riscv-vsetvl.cc
+++ b/gcc/config/riscv/riscv-vsetvl.cc
@@ -3282,6 +3282,1
No. we can't.
My goal is to forbid this following situation:
bb 2:
EMPTY (no any vsetvl and rvv insn)
bb 3:
user vsetvl.
We forbid user vsetvl (bb 3) be move to bb 2 in earliest fusion since user
vsetvl has no side effects
and we believe user vsetvl in bb 3 here is early enough.
However, if we
