[all-commits] [llvm/llvm-project] 8150ab: [LoopVectorize] Use CodeSize as the cost kind for ...

[John Brawn via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 8150ab93f7411009cc919022d2937d206a2f4359
      https://github.com/llvm/llvm-project/commit/8150ab93f7411009cc919022d2937d206a2f4359
  Author: John Brawn <john.brawn at arm.com>
  Date:   2025-02-27 (Thu, 27 Feb 2025)

  Changed paths:
    M llvm/lib/Transforms/Vectorize/LoopVectorize.cpp
    M llvm/lib/Transforms/Vectorize/VPlan.cpp
    M llvm/lib/Transforms/Vectorize/VPlanHelpers.h
    A llvm/test/Transforms/LoopVectorize/AArch64/optsize_minsize.ll
    A llvm/test/Transforms/LoopVectorize/ARM/optsize_minsize.ll

  Log Message:
  -----------
  [LoopVectorize] Use CodeSize as the cost kind for minsize (#124119)

Functions marked with minsize should aim for minimum code size, so the
vectorizer should use CodeSize for the cost kind and also the cost we
compare should be the cost for the entire loop: it shouldn't be divided
by the number of vector elements and block costs shouldn't be divided by
the block probability.

Possibly we should also be doing this for optsize as well, but there are
a lot of tests that assume the current behaviour and the definition of
optsize is less clear than minsize (for minsize the goal is to "keep the
code size of this function as small as possible" whereas for optsize
it's "keep the code size of this function low").



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications