Skip to content

Commit 747cb61

Browse files
committed
fixup! [mlir][vector][docs] Document indexed vs. non-indexed arguments
Define _indexed_
1 parent 7b273b0 commit 747cb61

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

mlir/docs/Dialects/Vector.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -320,7 +320,12 @@ There is **no consistent way** to identify:
320320
A more consistent way to classify "to", "from", and "value-to-store" arguments
321321
is by determining whether an operand is _indexed_ or _non-indexed_.
322322

323-
#### **Example: `vector.transfer_read` and `vector.transfer_write`**
323+
The distinction is somewhat intuitive, but for clarity:
324+
- Indexed operands require indices to specify an element/slice (e.g., `%A[0]`).
325+
- Non-indexed operands do not require indices as they are accessed in their
326+
entirety (e.g., `%B`).
327+
328+
Below is an example using: `vector.transfer_read` and `vector.transfer_write`
324329
```mlir
325330
Indexed Operand
326331
|

0 commit comments

Comments
 (0)