David Green bd4b61efbd [CostModel] Remove VF from IntrinsicCostAttributes ... getIntrinsicInstrCost takes a IntrinsicCostAttributes holding various parameters of the intrinsic being costed. It can either be called with a scalar intrinsic (RetTy==Scalar, VF==1), with a vector instruction (RetTy==Vector, VF==1) or from the vectorizer with a scalar type and vector width (RetTy==Scalar, VF>1). A RetTy==Vector, VF>1 is considered an error. Both of the vector modes are expected to be treated the same, but because this is confusing many backends end up getting it wrong. Instead of trying work with those two values separately this removes the VF parameter, widening the RetTy/ArgTys by VF used called from the vectorizer. This keeps things simpler, but does require some other modifications to keep things consistent. Most backends look like this will be an improvement (or were not using getIntrinsicInstrCost). AMDGPU needed the most changes to keep the code from c230965ccf working. ARM removed the fix in dfac521da1, webassembly happens to get a fixup for an SLP cost issue and both X86 and AArch64 seem to now be using better costs from the vectorizer. Differential Revision: https://reviews.llvm.org/D95291		2021-02-23 13:03:26 +00:00
..
lit.local.cfg	Reland "[SLPVectorizer] Pre-commit a test for D85759"	2020-08-11 12:18:33 -07:00
no-vectorize-rotate.ll	[CostModel] Remove VF from IntrinsicCostAttributes	2021-02-23 13:03:26 +00:00