| Issue |
156614
|
| Summary |
[mlir][lit] Is "CHECK-LITERAL" as correct FileCheck directive?
|
| Labels |
|
| Assignees |
|
| Reporter |
liyingyue0908
|
https://github.com/llvm/llvm-project/blob/0909f04dcec436a7956a86300eaaaac6fbfd681c/mlir/test/Dialect/Builtin/Bytecode/attrs.mlir#L89
Found a lit test with _expression_ "CHECK-LITERAL"
```
// CHECK-LABEL: @TestSparseElements
module @TestSparseElements attributes {
// CHECK-LITERAL: bytecode.sparse = sparse<[[0, 0], [1, 2]], [1, 5]> : tensor<3x4xi32>
bytecode.sparse = sparse<[[0, 0], [1, 2]], [1, 5]> : tensor<3x4xi32>
} {}
```
Is it a typo or "// CHECK-LITERAL: " should work for some versions?
We have some `CHECK-LITERAL` on own private mlir-based code. Confirming if they are supposed to be replaced by `CHECK{LITERAL}`
![]()
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
