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

[Jacob Yu]

================
@@ -82,6 +82,16 @@ def GenericOp : LinalgStructuredBase_Op<"generic", [
         types:
           parallel, reduction, window
 
+    Any element within the output operands that are not indexed by the 
----------------
pingshiyu wrote:

Seems to me like that leaves two options:
- If both the existing bufferization transformation and the transformation from @adam-smnk are valid, then it would actually be a semantics issue IMO, since what gets written in the unindexed elements depends on the specific pass used
- If the existing bufferization transformation is not valid, then that's a bug in the bufferization pass
@MaheshRavishankar @ftynse any I'm not familiar enough with linalg to comment on this, do you guys have any thoughts?

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