diff options
| author | Florian Hahn <flo@fhahn.com> | 2023-04-18 10:29:17 +0100 |
|---|---|---|
| committer | Florian Hahn <flo@fhahn.com> | 2023-04-18 10:29:31 +0100 |
| commit | ff0ec4f42ea035253684183a0e8de9d87ef7111a (patch) | |
| tree | 5eef286883cd702cfe05e75f906aa58d779df6c1 /llvm/lib/Support/CommandLine.cpp | |
| parent | d8c49d2ac9dd4f3f3ec92fcd5751e850d8d7172c (diff) | |
| download | llvm-ff0ec4f42ea035253684183a0e8de9d87ef7111a.zip llvm-ff0ec4f42ea035253684183a0e8de9d87ef7111a.tar.gz llvm-ff0ec4f42ea035253684183a0e8de9d87ef7111a.tar.bz2 | |
Recommit "[VPlan] Unify Value2VPValue and VPExternalDefs maps (NFCI)."
This reverts the revert commit 8c2276f89887d0a27298a1bbbd2181fa54bbb509.
The updated patch re-orders the getDefiningRecipe check in getVPalue to avoid
a use-after-free.
Original commit message:
Before this patch, a VPlan contained 2 mappings for Values -> VPValue:
1) Value2VPValue and 2) VPExternalDefs.
This duplication is unnecessary and there are already cases where
external defs are added to Value2VPValue. This patch replaces all uses
of VPExternalDefs with Value2VPValue.
It clarifies the naming of getOrAddVPValue (to getOrAddExternalVPValue)
and addVPValue (to addExternalVPValue).
At the moment, this is NFC, but will enable additional simplifications
in D147783.
Depends on D147891.
Reviewed By: Ayal
Differential Revision: https://reviews.llvm.org/D147892
Diffstat (limited to 'llvm/lib/Support/CommandLine.cpp')
0 files changed, 0 insertions, 0 deletions