[PATCH] RISC-V: In pipeline scheduling, insns should not be fusion in different BB blocks.

When the last insn1 of BB1 and the first insn2 of BB2 are fusion, insn2 will clear all dependencies in the function chain_to_prev_insn, resulting in insn2 may mov to any BB, and the program calculation result is wrong. gcc/ChangeLog: * sched-deps.cc (sched_macro_fuse_insns): Insns should

Re: [PATCH] RISC-V: In pipeline scheduling, insns should not be fusion in different BB blocks.

Jin Ma writes: > When the last insn1 of BB1 and the first insn2 of BB2 are fusion, insn2 will > clear all dependencies in the function chain_to_prev_insn, resulting in insn2 > may mov to any BB, and the program calculation result is wrong. > > gcc/ChangeLog: > > * sched-deps.cc (sched_macro_

Re: [PATCH] RISC-V: In pipeline scheduling, insns should not be fusion in different BB blocks.

On 5/25/23 03:22, Richard Sandiford wrote: Jin Ma writes: When the last insn1 of BB1 and the first insn2 of BB2 are fusion, insn2 will clear all dependencies in the function chain_to_prev_insn, resulting in insn2 may mov to any BB, and the program calculation result is wrong. gcc/ChangeLog:

Re: [PATCH] RISC-V: In pipeline scheduling, insns should not be fusion in different BB blocks.

On 5/25/23 02:32, Jin Ma wrote: When the last insn1 of BB1 and the first insn2 of BB2 are fusion, insn2 will clear all dependencies in the function chain_to_prev_insn, resulting in insn2 may mov to any BB, and the program calculation result is wrong. gcc/ChangeLog: * sched-deps.cc (s