[all-commits] [llvm/llvm-project] 690b0b: [LV] Add initial costs for VPInstructionWithType::...

[David Sherwood via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 690b0b0c63125aaf6b517df9d528789bb8c9c08a
      https://github.com/llvm/llvm-project/commit/690b0b0c63125aaf6b517df9d528789bb8c9c08a
  Author: David Sherwood <david.sherwood at arm.com>
  Date:   2026-06-10 (Wed, 10 Jun 2026)

  Changed paths:
    M llvm/lib/Transforms/Vectorize/VPlan.h
    M llvm/lib/Transforms/Vectorize/VPlanRecipes.cpp
    M llvm/test/Transforms/LoopVectorize/RISCV/force-vect-msg.ll
    M llvm/test/Transforms/LoopVectorize/RISCV/gather-scatter-cost.ll
    M llvm/test/Transforms/LoopVectorize/RISCV/tail-folding-gather-scatter.ll
    M llvm/test/Transforms/LoopVectorize/cast-costs.ll
    M llvm/test/Transforms/LoopVectorize/vscale-cost.ll

  Log Message:
  -----------
  [LV] Add initial costs for VPInstructionWithType::computeCost (#198291)

I noticed this was previously always returning a cost of 0
due to fear of triggering the (now deleted) legacy/vplan
cost model assert. Since the assert has now been removed
this should be safe to implement properly. I haven't
filled in the costs for all types yet, since there is
currently no way to expose those code paths. I suspect
for things like VPInstruction::StepVector the recipe is
always in the vector preheader and we never ask for its
cost.



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