diff options
author | Florian Hahn <flo@fhahn.com> | 2025-09-29 09:08:09 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-09-29 08:08:09 +0000 |
commit | b4be7ecaf06bfcb4aa8d47c4fda1eed9bbe4ae77 (patch) | |
tree | 8fca04e04ec1ba0a5b2a6f396cde8b596bf7af91 /llvm/lib/Support/VirtualFileSystem.cpp | |
parent | f92c23d713c048f8729b66310ea3fef9715f16e5 (diff) | |
download | llvm-b4be7ecaf06bfcb4aa8d47c4fda1eed9bbe4ae77.zip llvm-b4be7ecaf06bfcb4aa8d47c4fda1eed9bbe4ae77.tar.gz llvm-b4be7ecaf06bfcb4aa8d47c4fda1eed9bbe4ae77.tar.bz2 |
[VPlan] Compute cost of more replicating loads/stores in ::computeCost. (#160053)
Update VPReplicateRecipe::computeCost to compute costs of more
replicating loads/stores.
There are 2 cases that require extra checks to match the legacy cost
model:
1. If the pointer is based on an induction, the legacy cost model passes
its SCEV to getAddressComputationCost. In those cases, still fall back
to the legacy cost. SCEV computations will be added as follow-up
2. If a load is used as part of an address of another load, the legacy
cost model skips the scalarization overhead. Those cases are currently
handled by a usedByLoadOrStore helper.
Note that getScalarizationOverhead also needs updating, because when the
legacy cost model computes the scalarization overhead, scalars have not
been collected yet, so we can't each for replicating recipes to skip
their cost, except other loads. This again can be further improved by
modeling inserts/extracts explicitly and consistently, and compute costs
for those operations directly where needed.
PR: https://github.com/llvm/llvm-project/pull/160053
Diffstat (limited to 'llvm/lib/Support/VirtualFileSystem.cpp')
0 files changed, 0 insertions, 0 deletions