diff options
| author | Luke Lau <luke@igalia.com> | 2024-12-17 11:02:55 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-12-17 11:02:55 +0800 |
| commit | fba3e069b4ed38b16754d5e45837bfec9d5a372a (patch) | |
| tree | bf271de9cd2d43b97e549057d9a47900886665b3 /llvm/lib/CodeGen/StackMaps.cpp | |
| parent | bf700c39d1c9f88387bfe2ec4567567397200ea3 (diff) | |
| download | llvm-fba3e069b4ed38b16754d5e45837bfec9d5a372a.zip llvm-fba3e069b4ed38b16754d5e45837bfec9d5a372a.tar.gz llvm-fba3e069b4ed38b16754d5e45837bfec9d5a372a.tar.bz2 | |
[VPlan] Remove overlapping VPInstruction::mayWriteToMemory. NFCI (#120039)
VPInstruction has a definition of mayWriteToMemory, which seems to only
be used by VPlanSLP. However VPInstructions are already handled in
VPRecipeBase::mayWriteToMemory, and everywhere else seems to use this
definition. I think these should be the same for all intents and
purposes. The VPRecipeBase definition is more conservative but returns
true for stores/calls/invokes/SLPStores.
Diffstat (limited to 'llvm/lib/CodeGen/StackMaps.cpp')
0 files changed, 0 insertions, 0 deletions