+1
(binding)
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/11415#issuecomment-1135144482
You are receiving this because you are subscribed to this thread.
Message ID:
This is a formal vote thread to determine committer and PMC support for
[Quarterly Releases RFC](https://github.com/apache/tvm-rfcs/pull/67). Replying
+1 here means you support the RFC and we should merge it. This vote thread is
due to the fact that the RFC proposes a change in the way the commu
Great. let's move this to a PMC voting thread.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/67#issuecomment-1135022404
You are receiving this because you are subscribed to this thread.
Message ID:
great! so I think we just need some updates to the text of the RFC based on
discusison, then we are good to merge.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/71#issuecomment-1134999125
You are receiving this because you are subscribed to this th
```
backendA= MyUMABackendA()
backendB= MyUMABackendB()
backendA.register()
backendB.register()
mod = backendA.partition(mod)
mod = backendB.partition(mod)
```
Ah, that's the example I was missing (sorry!). After registration I think
calling backend.partition or letting CollagePartition 'do it fo
@junrushao1994 yep, we will post meeting notes here per the TVM Community
Meeting
[guidelines](https://docs.google.com/document/d/179l1WzqDiLXjjLmLopvxBSr0ylFS2plyXbeTtB8CteM/edit#heading=h.yjcjro6m0xi3).
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/p
Merged #73 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/73#event-6662679591
You are receiving this because you are subscribed to this thread.
Message ID:
Merged #69 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/69#event-6662507785
You are receiving this because you are subscribed to this thread.
Message ID:
> I think the main outstanding thing is the question of support here. I'd love
> for a few more folks to weigh in, tagging a few folks who may have ideas:
> @tqchen @jroesch @kparzysz-quic @u99127 @Mousius @leandron @comaniac @zhiics
> @Hzfengsy @ZihengJiang @yzhliu @masahi @icemelon
>
> broadl
> ok for A1 i'm good with named phases and we can modify as necessary. i think
> the A2.2 solution of directly registering target attrs makes sense to me. is
> that the direction we're aligned on here?
we can discuss this next week at the community meeting, or if we're in
alignment on these two
Thanks @mbs-octoml for this detailed explanation. Being a Collage-supported
backend is definitely something we want to achieve for UMA-integrated backends.
> The registration of patterns will need to support the existing triple of
> (pattern name, pattern, predicate) since the predicates are nec
11 matches
Mail list logo
