[mlir][lit] Is "CHECK-LITERAL" as correct FileCheck directive? #156614
Description
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}