> On Fri, 23 Dec 2022, Jose E. Marchesi wrote: > >> > (scheduling across calls in sched2 is somewhat dubious as well, but >> > it doesn't risk register pressure issues, and on VLIW CPUs it at least >> > can result in better VLIW packing) >> >> Does sched2 actually schedule across calls? All the comments in the >> source code stress the fact that the second scheduler pass (after >> register allocation) works in regions that correspond to basic blocks: >> "(after reload, each region is of one block)". > > A call instruction does not end a basic block.
Ok, so my original assumption in the patch explaining why I disabled sched1 but not sched2 was not correct. Good to know. > (also, with -fsched2-use-superblocks sched2 works on regions like sched1) > > Alexander
