[all-commits] [llvm/llvm-project] 8555c9: [X86] Use more accurate increments for the inducti...

[topperc via All-commits]

  Branch: refs/heads/master
  Home:   https://github.com/llvm/llvm-project
  Commit: 8555c91337523656c011dd13a8dfc9319c71fdae
      https://github.com/llvm/llvm-project/commit/8555c91337523656c011dd13a8dfc9319c71fdae
  Author: Craig Topper <craig.topper at intel.com>
  Date:   2020-05-01 (Fri, 01 May 2020)

  Changed paths:
    M llvm/test/CodeGen/X86/sad.ll

  Log Message:
  -----------
  [X86] Use more accurate increments for the induction variables in sad.ll. NFC

I think some copy/pasting was used to create loops of different
VFs. But the increment of the induction variable wasn't updated
to match the VF.

This has no effect on the pattern matching we're testing, it just
helps the test make sense to the reader.


  Commit: e39c7ab2b9c39acc9e793fdfe5d531cef6798743
      https://github.com/llvm/llvm-project/commit/e39c7ab2b9c39acc9e793fdfe5d531cef6798743
  Author: Craig Topper <craig.topper at intel.com>
  Date:   2020-05-01 (Fri, 01 May 2020)

  Changed paths:
    M llvm/include/llvm/CodeGen/BasicTTIImpl.h
    M llvm/test/Analysis/CostModel/ARM/cast.ll
    M llvm/test/Analysis/CostModel/X86/arith-fix.ll
    M llvm/test/Analysis/CostModel/X86/arith-overflow.ll
    M llvm/test/Analysis/CostModel/X86/cast.ll
    M llvm/test/Analysis/CostModel/X86/extend.ll
    M llvm/test/Analysis/CostModel/X86/fptosi.ll
    M llvm/test/Analysis/CostModel/X86/fptoui.ll
    M llvm/test/Analysis/CostModel/X86/masked-intrinsic-cost.ll
    M llvm/test/Analysis/CostModel/X86/min-legal-vector-width.ll
    M llvm/test/Analysis/CostModel/X86/sitofp.ll
    M llvm/test/Analysis/CostModel/X86/trunc.ll
    M llvm/test/Analysis/CostModel/X86/uitofp.ll

  Log Message:
  -----------
  [CostModel][X86][ARM] Teach default implementation of getCastInstrCost to not add a split/join cost if source type and the destination type both have a SplitVector action

If both the source and the destination need to be split then the two halves of the split operation are completely independent and don't need to be split or joined. So we don't need to assess a cost for the split or join.

Differential Revision: https://reviews.llvm.org/D79111


Compare: https://github.com/llvm/llvm-project/compare/999f04ce347c...e39c7ab2b9c3