Lunderberg commented on code in PR #12720:
URL: https://github.com/apache/tvm/pull/12720#discussion_r965325566
##########
python/tvm/tir/schedule/schedule.py:
##########
@@ -2479,6 +2480,20 @@ def transform_layout(
primitive will be called in addition to the
TransformLayout primitive.
+ pad_value: Optional[Union[int, float, PrimExpr, IndexMap, Callable]]
+
+ The value to be used for any padding introduced by the
+ transformation.
+
+ If None, the transformation may not introduce padding.
+
+ If an int, float or PrimExpr, the transformation is the
+ specific value to be present in the padding.
+
+ If an IndexMap or Callable, the transformation is the
+ value to be present in the padding in terms of the
+ transformed index.
Review Comment:
Good point. I had been thinking of it as the `(const Array<Var>&, const
Array<PrimExpr>&)` call signature on the TE side for the transformation, and
was avoiding introducing additional structures. I had forgotten that the TIR
schedule accepts an `IndexMap` for the transformation, and agree that the C++
side would be better expressed as an `Optional<IndexMap>` instead.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
