We are adding more and more operation actions for different sub-features, and they are scatter over different places without clean logic.
if (hasVSX()) ... if (hasP9Vector()) ... ... if (hasVSX()) ...
This NFC patch tried to set operation actions as following order:
By default -> hasAltivec -> hasVSX -> hasP8Altivec() -> hasP8Vector() -> hasP9Altivec() -> hasP9Vector()
So that, some operation actions could be override later and we will have clean picture on the place that setOperationAction should be added.
These are not guarded by any predicate, why move them?