[TTI] Use OperandValueInfo in getMemoryOpCost client api [nfc]
authorPhilip Reames <preames@rivosinc.com>
Mon, 22 Aug 2022 18:20:14 +0000 (11:20 -0700)
committerPhilip Reames <listmail@philipreames.com>
Mon, 22 Aug 2022 18:26:31 +0000 (11:26 -0700)
commit27d3321c4fef62f567d29e88cd44fc1d92c6b6a5
treedf31e246af62e7686c842dcfefcbb5d51b0ff2f5
parent71771f8510b62ef999db62ecc2318ec9d7ff878c
[TTI] Use OperandValueInfo in getMemoryOpCost client api [nfc]

This removes the last use of OperandValueKind from the client side API, and (once this is fully plumbed through TTI implementation) allow use of the same properties in store costing as arithmetic costing.
llvm/include/llvm/Analysis/TargetTransformInfo.h
llvm/lib/Analysis/TargetTransformInfo.cpp
llvm/lib/Transforms/Vectorize/LoopVectorize.cpp
llvm/lib/Transforms/Vectorize/SLPVectorizer.cpp