cc @ zxybazh since you authored the Target system, cc @zhiics @comaniac as it
is related to BYOC
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/38#issuecomment-939150864
More notes to self:
- You can get the device_type for a Target from target_kind->device_type.
Somehow I missed that very obvious fact.
- Eric has a very nice write-up explaining devices vs targets vs device api at
docs/dev/device_target_interactions.rst
--
You are receiving this because you
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, unde
I don't have other comments :-) Going to merge this RFC in 24h if there is no
objection
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/41#issuecomment-939069224
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?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly o
