On Sat, Mar 30, 2019 at 09:00:15AM +1300, Michael Cree wrote: > It does move the umulh inside the loop but that seems sensible since > the use of unlikely() implies that the loop is unlikely to be taken > so on average it would be a good bet to start the calculation of > umulh earlier since it has a few cycles latency to get the result, > and it is pipelined so it can be calculated in the shadow of the > mulq instruction on the same execution unit. That may make sense, but it is not what happens, sorry. It _starts off_ as part of the loop, and it is never moved outside. The only difference between a likely loop and an unlikely loop here I've seen (on all targets I tried) is that with a likely loop the loop target is aligned, while with an unlikely loop it isn't. > On the older CPUs > (before EV6 which are not out-of-order execution) having the umulh > inside the loop may be a net gain. Yes. Similarly, on Power you can often calculate the high mul at the same time as the low mul, for no extra cost. This may be true on many archs. Segher
