[Mlir-commits] [mlir] [mlir][linalg] added some conditions for values being undefined in the documentation for `linalg.generic` (PR #96251)

[Oleksandr Alex Zinenko]

================
@@ -82,6 +82,11 @@ def GenericOp : LinalgStructuredBase_Op<"generic", [
         types:
           parallel, reduction, window
 
+    Any values within the output operands that are not unindexed by the 
----------------
ftynse wrote:

I can't understand the double negation in "not unindexed".

Otherwise, nothing currently precludes a "diagonal" `(d0, d1) -> (d0, d0)` indexing map for the result. The iteration dimension associated with `d1` can be inferred from another operand/result so the iteration space is fully defined. So while the iteration space is indeed computed from data, it doesn't necessarily imply that the index space of each individual operand/result is fully covered by the mapping from the iteration space (which should be noted somewhere as a requirement for results but not operands).

https://github.com/llvm/llvm-project/pull/96251