![]() The min/max intrinsics are not yet canonical, but when they are the tail predications analysis will change from treating them like icmp to treating them like intrinsics. Unfortunately, they can currently produce better code by not being tail predicated thanks to the vectorizer picking higher VF's and the backend folding to better instructions (especially for saturate patterns). In the long run we will need to improve the vectorizers cost modelling, recognizing the instruction directly, but in the meantime this treats min/max as before to prevent performance regressions. |
||
---|---|---|
.. | ||
arm_add_q7.ll | ||
arm_fill_q7.ll | ||
arm_mult_q15.ll | ||
lit.local.cfg | ||
mve-floatreduce.ll |