[mlir][test] Add comments in a test (nfc)

[banach-space]

Documents which patterns are tested in:

• vector-transfer-collapse-inner-most-dims.mlir.

[llvmbot]

@llvm/pr-subscribers-mlir

@llvm/pr-subscribers-mlir-vector

Author: Andrzej Warzyński (banach-space)

Changes

Adds a note to document which patterns are tested in

• vector-transfer-collapse-inner-most-dims.mlir.

---

Full diff: https://github.com/llvm/llvm-project/pull/99810.diff

1 Files Affected:

• (modified) mlir/test/Dialect/Vector/vector-transfer-collapse-inner-most-dims.mlir (+2)

diff --git a/mlir/test/Dialect/Vector/vector-transfer-collapse-inner-most-dims.mlir b/mlir/test/Dialect/Vector/vector-transfer-collapse-inner-most-dims.mlir
index 3f36756fe95d7..cd56c1bf9695b 100644
--- a/mlir/test/Dialect/Vector/vector-transfer-collapse-inner-most-dims.mlir
+++ b/mlir/test/Dialect/Vector/vector-transfer-collapse-inner-most-dims.mlir
@@ -2,6 +2,7 @@
 
 //-----------------------------------------------------------------------------
 // 1. vector.transfer_read
+// [Pattern: DropInnerMostUnitDimsTransferRead]
 //-----------------------------------------------------------------------------
 
 func.func @contiguous_inner_most(%src: memref<1x1x8x1xf32, strided<[3072, 8, 1, 1], offset: ?>>) -> vector<1x8x1xf32>{
@@ -306,6 +307,7 @@ func.func @negative_non_unit_strides(%src: memref<512x16x1xf32, strided<[8192, 1
 
 //-----------------------------------------------------------------------------
 // 2. vector.transfer_write
+// [Pattern: DropInnerMostUnitDimsTransferWrite]
 //-----------------------------------------------------------------------------
 
 func.func @contiguous_inner_most(%dest: memref<1x512x16x1x1xf32>, %v: vector<1x16x16x1x1xf32>, %i: index) {

[jpienaar]

This makes me wonder if we could almost do something automated (with debugging enabled the patterns are reported, per function getting the patterns that applied as post processing should be doable)

[banach-space]

This makes me wonder if we could almost do something automated (with debugging enabled the patterns are reported, per function getting the patterns that applied as post processing should be doable)

Funnily enough, it's the -debug dump that I got the pattern names from. But I'd need some quality time with the pattern rewriter driver (or pointers from sb) to implement a dedicated options for this (e.g. -debug-list-successeful-patterns). Thanks for +1!