[all-commits] [llvm/llvm-project] 37dfc4: [NFC] LoopVectorizationCostModel::getMaximizedVFFo...

[Roman Lebedev via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 37dfc467ac807bde4f221edbf304d9a46c9789b2
      https://github.com/llvm/llvm-project/commit/37dfc467ac807bde4f221edbf304d9a46c9789b2
  Author: Roman Lebedev <lebedev.ri at gmail.com>
  Date:   2021-06-17 (Thu, 17 Jun 2021)

  Changed paths:
    M llvm/lib/Transforms/Vectorize/LoopVectorize.cpp

  Log Message:
  -----------
  [NFC] LoopVectorizationCostModel::getMaximizedVFForTarget(): clarify debug msg

This really isn't talking about vectors in general,
but only about either fixed or scalable vectors,
and it's pretty confusing to see it state
that there aren't any vectors :)


  Commit: 69caacc626f7dbbb9223b370952fcf5660e242dc
      https://github.com/llvm/llvm-project/commit/69caacc626f7dbbb9223b370952fcf5660e242dc
  Author: Roman Lebedev <lebedev.ri at gmail.com>
  Date:   2021-06-17 (Thu, 17 Jun 2021)

  Changed paths:
    M llvm/lib/Target/X86/X86ScheduleZnver3.td

  Log Message:
  -----------
  [X86] AMD Zen 3: don't confuse shift and shuffle, NFC

These proc res groups occupy the exact same pipes,
so this doesn't affect the modelling,
but it's confusing nontheless.


Compare: https://github.com/llvm/llvm-project/compare/4e2aee8d3bab...69caacc626f7