[all-commits] [llvm/llvm-project] 39c8e8: [VPlan] Move recording of Inst->VPValue to VPRecip...

[Florian Hahn via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 39c8e87717fbc611b9e84f62edf656608ae52e5c
      https://github.com/llvm/llvm-project/commit/39c8e87717fbc611b9e84f62edf656608ae52e5c
  Author: Florian Hahn <flo at fhahn.com>
  Date:   2024-03-23 (Sat, 23 Mar 2024)

  Changed paths:
    M llvm/lib/Transforms/Vectorize/LoopVectorize.cpp
    M llvm/lib/Transforms/Vectorize/VPRecipeBuilder.h
    M llvm/lib/Transforms/Vectorize/VPlan.h
    M llvm/lib/Transforms/Vectorize/VPlanTransforms.cpp

  Log Message:
  -----------
  [VPlan] Move recording of Inst->VPValue to VPRecipeBuilder (NFCI). (#84464)

Instead of keeping a mapping of Inst->VPValues (of their corresponding
recipes) in VPlan's Value2VPValue mapping, keep it in VPRecipeBuilder
instead. After recently replacing the last user of this mapping after
initial construction, this mapping is only needed for recipe
construction (to map IR operands to VPValue operands).

By moving the mapping, VPlan's VPValue tracking can be simplified and
limited only to live-ins. It also allows removing disableValue2VPValue
and associated machinery & asserts.

PR: https://github.com/llvm/llvm-project/pull/84464



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