Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
I have a suspicion that operand insertion may write out of bounds. Please add a test for a tiled loop that has a mix of tensors and non-tensors as inputs.
Tests for user-visible error messages are also welcome, as usual.
mlir/lib/Dialect/Linalg/Transforms/ComprehensiveBufferize.cpp | ||
---|---|---|
1784–1787 | Nit: expand auto here. | |
1785 | The indexing here looks suspicious in case of non-tensor operands. Such operands will be skipped at entry of the loop, but index is still contiguous. So it will not insert the new input operand after the last inserted input operand, but later, potentially out of bounds. | |
1788 | Same indexing question as above. | |
1793 | Shouldn't this also remove the original tensor inputs from the loop? Or a canonicalization is expected to handle that later? If the latter, it is worth mentioning in the comment. |
The indexing here looks suspicious in case of non-tensor operands. Such operands will be skipped at entry of the loop, but index is still contiguous. So it will not insert the new input operand after the last inserted input operand, but later, potentially out of bounds.