[all-commits] [llvm/llvm-project] 27d332: [TTI] Use OperandValueInfo in getMemoryOpCost clie...

[Philip Reames via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 27d3321c4fef62f567d29e88cd44fc1d92c6b6a5
      https://github.com/llvm/llvm-project/commit/27d3321c4fef62f567d29e88cd44fc1d92c6b6a5
  Author: Philip Reames <preames at rivosinc.com>
  Date:   2022-08-22 (Mon, 22 Aug 2022)

  Changed paths:
    M llvm/include/llvm/Analysis/TargetTransformInfo.h
    M llvm/lib/Analysis/TargetTransformInfo.cpp
    M llvm/lib/Transforms/Vectorize/LoopVectorize.cpp
    M llvm/lib/Transforms/Vectorize/SLPVectorizer.cpp

  Log Message:
  -----------
  [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.