+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12651#issuecomment-1233667253
You are receiving this because you commented.
Message ID:
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12651#issuecomment-1233605463
You are receiving this because you commented.
Message ID:
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12651#issuecomment-1233603370
You are receiving this because you commented.
Message ID:
Merged #88 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/88#event-7300385635
You are receiving this because you are subscribed to this thread.
Message ID:
Closed #12583 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12583#event-7300381798
You are receiving this because you are subscribed to this thread.
Message ID:
The vote has passed, therefore I'll merge this RFC. @gromero please create a
tracking issue (you can create another PR to add it to this doc).
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/88#issuecomment-1233535253
You are receiving this because y
The 7-day voting period has concluded. The votes are as follows:
+1:
Leandro
Thierry
Chris Sullivan
TQ
David
Siyuan
Junru
Masa
Manupa
Luke
Matthew Barrett
Eric Lunderberg
0:
Andrew Luo
Krzysztof
Xiyou
-1:
none
The vote has passed.
--
Reply to this email directly or view it on GitHub:
https://
+1 (binding)
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12651#issuecomment-1233389506
You are receiving this because you commented.
Message ID:
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12651#issuecomment-1233388156
You are receiving this because you commented.
Message ID:
[Rendered
link](https://github.com/gromero/tvm-rfcs/blob/cmg/rfcs/0088-commit-message-guideline.md)
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/88#issuecomment-1233170752
You are receiving this because you are subscribed to this thread.
Message
Thanks @areusch , the particular section that you described was explicitly
listed as "future opportunities" and is not part of the RFC which may or may
not be executed. As per stated in the text
```
This section describes possible approaches to evolve the default build to
leverage more of unit
-1 (binding veto)
I agree with @leandron that Establish TVM Unity Connection Technical Strategy
RFC is heavily centered around Relax RFC. Additionally, while this RFC stops
short of endorsing the Relax RFC as the future direction of TVM, it very
[explicitly
discusses](https://github.com/apache
Thank you @leandron . As per stated in the beginning, this RFC establishes a
strategy to introduce an optional module to TVM, which as of now is minimally
disruptive to the current infrastructure.
We also consider it as as a separate RFC from the relax RFC it sets up the
overall technical stra
-1 (binding veto)
There is overlap with what is being proposed here being a superset of what is
under active discussion in the Relax RFC at
https://github.com/apache/tvm-rfcs/pull/89, so I don't think that we can make
an informed decision in this RFC, until the discussion in the Relax RFC are
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12651#issuecomment-1232590059
You are receiving this because you commented.
Message ID:
+1
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/12651#issuecomment-1232578723
You are receiving this because you commented.
Message ID:
16 matches
Mail list logo
