areusch commented on a change in pull request #31:
URL: https://github.com/apache/tvm-rfcs/pull/31#discussion_r720859082
##########
File path: rfcs/0031-devices-api.md
##########
@@ -306,6 +293,8 @@ Another route to take is to treat RTOSes as entirely
separate from TVM, requirin
# Unresolved questions
[unresolved-questions]: #unresolved-questions
+Is coupling `Target`s with this Device API to the C Runtime acceptable? From
the authors point of view this seems an acceptable trade off given the devices
won't function correctly without the flow control.
Review comment:
sorry not yet :/. it's sort of teased in the future work section of my
[Artifact
pre-RFC](https://discuss.tvm.apache.org/t/introduce-artifact-a-container-for-generated-code/11099).
i'm more including this pointer here as an "early FYI" how i'd like to solve
this (e.g. using the TargetDevice name as the mechanism to bind a sub-target to
a Device API impl).
--
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]
