This patch is a simple piece of refactoring that now permits users
to create VPInstructions and specify the name of the value being
generated. This is useful for creating more readable/meaningful
names in IR.
Details
Details
Diff Detail
Diff Detail
Unit Tests
Unit Tests
Time | Test | |
---|---|---|
240 ms | x64 debian > BOLT.runtime/X86::user-func-reorder.c | |
60,430 ms | x64 debian > Clang.Driver::fsanitize.c |
Event Timeline
llvm/lib/Transforms/Vectorize/VPlan.h | ||
---|---|---|
798 | Is Twine something typically used as a storage type? Most instances seem to be for parameter passing. Which makes me wonder if the storage type should be std::string? |
Comment Actions
LGTM, thanks! I think eventually it would be desirable to keep track of names in a separate table so we don't have to keep those (optional) strings directly in the recipes (similar to LLVM IR value naming), but this seems like a good first step.
llvm/lib/Transforms/Vectorize/VPlanRecipes.cpp | ||
---|---|---|
256 | nit: unrelated whitespace change. |
Is Twine something typically used as a storage type? Most instances seem to be for parameter passing. Which makes me wonder if the storage type should be std::string?