[Mlir-commits] [mlir] [mlir][vector] Refactor vector-transfer-to-vector-load-store.mlir (NFC) (PR #105509)
Andrzej WarzyĆski
llvmlistbot at llvm.org
Wed Aug 21 09:05:15 PDT 2024
================
@@ -331,53 +331,52 @@ func.func @transfer_read_permutations(%arg0 : memref<?x?xf32>, %arg1 : memref<?x
}
// CHECK-LABEL: func @transfer_write_permutations
-// CHECK-SAME: %[[ARG0:.*]]: memref<?x?x?x?xf32>
-// CHECK-SAME: %[[ARG1:.*]]: tensor<?x?x?x?xf32>
-// CHECK-SAME: %[[ARG2:.*]]: vector<7x14x8x16xf32>
-// CHECK-SAME: %[[ARG3:.*]]: vector<8x16xf32>
-// CHECK-SAME: %[[M:.*]]: i1
+// CHECK-SAME: %[[MEM0:.*]]: memref<?x?x?x?xf32>
+// CHECK-SAME: %[[ARG1:.*]]: tensor<?x?x?x?xf32>
+// CHECK-SAME: %[[VEC0:.*]]: vector<7x14x8x16xf32>
+// CHECK-SAME: %[[VEC1:.*]]: vector<8x16xf32>
+// CHECK-SAME: %[[M:.*]]: i1
func.func @transfer_write_permutations(
- %arg0 : memref<?x?x?x?xf32>, %arg1 : tensor<?x?x?x?xf32>,
- %v1 : vector<7x14x8x16xf32>, %v2 : vector<8x16xf32>, %m: i1) -> tensor<?x?x?x?xf32> {
+ %mem_0 : memref<?x?x?x?xf32>, %arg1 : tensor<?x?x?x?xf32>,
----------------
banach-space wrote:
With Tensors I would normally use `%dest` or `%src`. Not sure what else could be a good match for `%vec` and `%mem` that we use for Vector and MemRef, respectively.
But, IMHO, there's a more confusing thing here ... mixing Tensor and MemRef semantics in one test. My suggestion would be to split into two tests.
https://github.com/llvm/llvm-project/pull/105509
More information about the Mlir-commits
mailing list