You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tvm.apache.org by GitBox <gi...@apache.org> on 2021/10/06 14:05:51 UTC
[GitHub] [tvm-rfcs] Lunderberg opened a new pull request #40: [RFC][TIR] 1-d AllocateNode::extent
Lunderberg opened a new pull request #40:
URL: https://github.com/apache/tvm-rfcs/pull/40
This RFC changes `Array<PrimExpr> AllocateNode::extents` to `PrimExpr AllocateNode::extent`, giving the 1-d size of the buffer to be allocated. This is part of the separation between logical layout and physical layout, proposed in [RFC#0039](https://github.com/apache/tvm-rfcs/pull/0039).
TODO: Rendered markdown link
--
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: commits-unsubscribe@tvm.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tvm-rfcs] vinx13 commented on pull request #40: [RFC][TIR] Change AllocateNode::extent to 1-D
Posted by GitBox <gi...@apache.org>.
vinx13 commented on pull request #40:
URL: https://github.com/apache/tvm-rfcs/pull/40#issuecomment-938810981
Thanks for the RFC. A quick question: RFC #39 mentioned the usage of `PHYSICAL_AXIS_SEPARATOR` to support n-d physical allocation (if supported by runtime), how will it work with 1-d extent here?
--
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: commits-unsubscribe@tvm.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tvm-rfcs] Lunderberg closed pull request #40: [RFC][TIR] Change AllocateNode::extent to 1-D
Posted by GitBox <gi...@apache.org>.
Lunderberg closed pull request #40:
URL: https://github.com/apache/tvm-rfcs/pull/40
--
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: commits-unsubscribe@tvm.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tvm-rfcs] Lunderberg commented on pull request #40: [RFC][TIR] Change AllocateNode::extent to 1-D
Posted by GitBox <gi...@apache.org>.
Lunderberg commented on pull request #40:
URL: https://github.com/apache/tvm-rfcs/pull/40#issuecomment-954215697
Closing this RFC, as it is no longer applicable after significant changes made to #39.
--
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: commits-unsubscribe@tvm.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tvm-rfcs] Lunderberg commented on pull request #40: [RFC][TIR] Change AllocateNode::extent to 1-D
Posted by GitBox <gi...@apache.org>.
Lunderberg commented on pull request #40:
URL: https://github.com/apache/tvm-rfcs/pull/40#issuecomment-939073862
This is the first in a series of proposed changes, and this one on its own won't be able to support the `PHYSICAL_AXIS_SEPARATOR`. In the [Impacted TIR Nodes](https://github.com/Lunderberg/tvm-rfcs/blob/data_layout/rfcs/0039-buffer-physical-layout.md#impacted-tir-nodes) section of RFC #39, under `AllocateNode`, it gives a description of the changes being made. This first change removes all information of the logical shape from the `AllocateNode`, and the follow-up change will then extend to allow for N-d physical shapes.
--
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: commits-unsubscribe@tvm.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org