Hi Vineet, > I agree the NARROW/WIDE stuff is obfuscating things in technicalities.
Is there evidence this change would make things significantly worse for some targets? I did a few runs on Neoverse V2 with various options and it looks beneficial both for integer and FP. On the example and options you mentioned I got 20.1% speedup! This is a very wide core, so wide vs narrow is not the right terminology as the gains are on both. > How about TARGET_SCHED_PRESSURE_SPILL_AGGRESSIVE with true (default) being > existing behavior > and false being new semantics. > Its a bit verbose but I think clear enough. Another option may be to treat it like a new type of pressure algorithm, eg. --param sched-pressure-algorithm=3 or update one of the existing ones. There are already too many features in the scheduler - it would be better to reduce the many variants and focus on doing really well on modern cores. Cheers, Wilco
