- Initiate the unit test with a test that tests various variants of build() methods generated for ops with variadic operands and results.
- The intent is to migrate unit .td tests in mlir/test/mlir-tblgen that check for generated C++ code to these unit tests which test both that the generated code compiles and also is functionally correct.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/unittests/TableGen/OpBuildGen.cpp | ||
---|---|---|
15 | clang-tidy: warning: #includes are not sorted properly [llvm-include-order] | |
155 | I couldn't quite follow the matrix being formed here {single variadic arg} x {single variadic result, multiple variadic results, non variadic result} ? I think you have a reason for this configuration, but it isn't clear just looking at the code why (for example) multiple variadic args need not be tested. Perhaps a comment would help there. |
I have added a comment explaining why I am testing these 3 combinations in particulat:
I think you have a reason for this configuration, but it isn't clear just looking at the code why (for example) multiple variadic args need not be tested.
In general, I'd expect that this test evolves to test all possible build methods, including for multiple variadic args, but it's not being done in this change.
clang-tidy: warning: #includes are not sorted properly [llvm-include-order]