llvm-project/llvm/unittests/Transforms/Vectorize
Florian Hahn 40e7bfc424 [VPlan] Use consecutive numbers to print VPValues instead of addresses.
Currently when printing VPValues we use the object address, which makes
it hard to distinguish VPValues as they usually are large numbers with
varying distance between them.

This patch adds a simple slot tracker, similar to the ModuleSlotTracker
used for IR values. In order to dump a VPValue or anything containing a
VPValue, a slot tracker for the enclosing VPlan needs to be created. The
existing VPlanPrinter can take care of that for the existing code. We
assign consecutive numbers to each VPValue we encounter in a reverse
post order traversal of the VPlan.

Reviewers: rengolin, hsaito, fhahn, Ayal, dorit, gilr

Reviewed By: gilr

Differential Revision: https://reviews.llvm.org/D73078
2020-03-05 14:55:15 +00:00
..
CMakeLists.txt [LV][VPlan] Change to implement VPlan based predication for 2019-01-23 22:43:12 +00:00
VPlanDominatorTreeTest.cpp
VPlanHCFGTest.cpp [VPlan] Add getPlan() to VPBlockBase. 2020-03-03 13:20:13 +00:00
VPlanLoopInfoTest.cpp
VPlanPredicatorTest.cpp [VPlan] Add getPlan() to VPBlockBase. 2020-03-03 13:20:13 +00:00
VPlanSlpTest.cpp [VPlan] Rename VPlanHCFGTransforms to VPlanTransforms (NFC). 2019-12-07 08:56:35 +00:00
VPlanTest.cpp [VPlan] Use consecutive numbers to print VPValues instead of addresses. 2020-03-05 14:55:15 +00:00
VPlanTestBase.h [llvm] Migrate llvm::make_unique to std::make_unique 2019-08-15 15:54:37 +00:00