[MLIR] Drop strict super-vector requirement in MaterializeVector

The strict requirement (i.e. at least 2 HW vectors in a super-vector) was a
premature optimization to avoid interfering with other vector code potentially
introduced via other means.

This CL avoids this premature optimization and the spurious errors it causes
when super-vector size == HW vector size (which is a possible corner case).

This may be revisited in the future.

PiperOrigin-RevId: 227763966

1 files changed, 1 insertions, 1 deletions

diff --git a/mlir/lib/Transforms/MaterializeVectors.cpp b/mlir/lib/Transforms/MaterializeVectors.cpp
index ebfdbc28d6c..bbe2f85319b 100644
--- a/mlir/lib/Transforms/MaterializeVectors.cpp
+++ b/mlir/lib/Transforms/MaterializeVectors.cpp
@@ -741,7 +741,7 @@ PassResult MaterializeVectorsPass::runOnFunction(Function *f) {
     if (!opInst.isa<VectorTransferWriteOp>()) {
       return false;
     }
-    return matcher::operatesOnStrictSuperVectors(opInst, subVectorType);
+    return matcher::operatesOnSuperVectors(opInst, subVectorType);
   };
   auto pat = Op(filter);
   auto matches = pat.match(f);