[llvm] [VPlan] Use parameter packs to avoid unary/binary/ternary matchers. NFC (PR #152272)
Florian Hahn via llvm-commits
llvm-commits at lists.llvm.org
Thu Aug 7 03:04:48 PDT 2025
================
@@ -270,251 +265,177 @@ struct Recipe_match {
}
};
-template <unsigned Opcode, typename... RecipeTys>
-using ZeroOpRecipe_match =
- Recipe_match<std::tuple<>, Opcode, false, RecipeTys...>;
-
-template <typename Op0_t, unsigned Opcode, typename... RecipeTys>
-using UnaryRecipe_match =
- Recipe_match<std::tuple<Op0_t>, Opcode, false, RecipeTys...>;
-
-template <typename Op0_t, unsigned Opcode>
-using UnaryVPInstruction_match =
- UnaryRecipe_match<Op0_t, Opcode, VPInstruction>;
+template <unsigned Opcode, typename... OpTys>
+using AllRecipe_match =
----------------
fhahn wrote:
Probably best to keep this in-line with IR PatternMatch, for which the default is also non-commutative w/o special naming I think.
https://github.com/llvm/llvm-project/pull/152272
More information about the llvm-commits
mailing list