This enables creating a replacement rule where range of positional replacements
need not be spelled out, or are not known (e.g., enable having a rewrite that
forward all operands to a call generically).
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/test/mlir-tblgen/rewriter-indexing.td | ||
---|---|---|
92 | I'm thinking the form like "$...", which maps all the remaining. so in this case, we don't need to write down v1 ~ v3. Will this be clear? In addition, for me, this form looks it will appear in something like, |
mlir/test/mlir-tblgen/rewriter-indexing.td | ||
---|---|---|
92 | Yes this one just changes it in the native call, not in the DAG specification. With ops we have an explicit and fixed set of args, today one would match them by name or elide in matching with $_. We can already use native codecall expansion without changing dag matching (so these are independent but could work together). A potential problem with the dag format is it would be confusing with variadics. |
Can you update the description to specifically mention that this is for NativeCodeCalls? It wasn't clear on the first read.
Can you also add documentation for this feature to the .md docs?
mlir/lib/TableGen/Format.cpp | ||
---|---|---|
101 | Can you just pass std::isdigit as is? | |
109 | Can you add a comment here on what this is? | |
181–185 | interleaveComma here? (using llvm::seq, or llvm::make_range on adaptors) | |
utils/bazel/llvm-project-overlay/mlir/BUILD.bazel | ||
1501 | This change looks unrelated. |
mlir/lib/TableGen/Format.cpp | ||
---|---|---|
101 | Depends on compiler, some yes others no it seems. Reverting to explicit lambda. |
mlir/lib/TableGen/Format.cpp | ||
---|---|---|
101 | (You should be able to use llvm::isDigit then) |
Can you just pass std::isdigit as is?