Add conversion tests and correctness tests.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Fly-by comment: standard dialect is no more, we should rename this pass, the related files and so on.
LGTM, but leaving the approval to our numerical expert
Also +1 on what Alex said, but that should be done in a separate refactoring that changes the name and switches....
(which can always have a wider impact than one thinks...)
mlir/lib/Conversion/ComplexToStandard/ComplexToStandard.cpp | ||
---|---|---|
927 | In this block of code, it would be helpful if you call out the subexpressions shown above explicitly, just to make reading this code easier on the eye |
mlir/test/Conversion/ComplexToStandard/convert-to-standard.mlir | ||
---|---|---|
738–775 | I do not think that this verbose test adds some value here. The integration test does. Could you remove in these two tests everything but CHECK-LABEL lines to know that the lowering happened but without all these details? |
Address review comments: use camelCase; add more comments; remove check for generated code in tests.
mlir/test/Conversion/ComplexToStandard/convert-to-standard.mlir | ||
---|---|---|
697 | The file before this PR doesn't have a newline either. But add a newline anyway. |
Top-level comments should use three slashes.