Hi, would you please retrigger the CI by sending an empty commit?
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/10308#issuecomment-1049605201
You are receiving this because you are subscribed to this thread.
Message ID:
Hi Chris,
is there a plan when the next TVM Community Meeting is going to take place?
Especially the "Remove CODEOWNERS" discussion seems to be a good fit for a
high-bandwidth discussion:
https://discuss.tvm.apache.org/t/rfc-remove-codeowners/12095/8
Thanks,
Michael
CC: @hogepodge @aca8
Hi @MJKlaiber ,
Apologies to for not getting back to this in time.
Thanks for the proposal! and it broadly looks like wrapping the Target Hooks
RFC (by @Mousius ) :
https://github.com/apache/tvm-rfcs/blob/main/rfcs/0010-target-registered-compiler-flow-customisation.md,
and exposing a nice/str
@driazati @areusch ,
This looks like a great suggestion!.
I think the proposal is about adding a mechanism to use the cc tag to attach
people as reviewers, which seems good step.
I agree with @comaniac by helping the new authors finding people to tag for
reviews rather than doing a mandator
Sure. @zxybazh
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/10308#issuecomment-1049924550
You are receiving this because you are subscribed to this thread.
Message ID:
@MJKlaiber I'm going to take on hosting the community meetings from Chris
shortly. I'm just checking on a few last things before posting up about it.
---
[Visit
Topic](https://discuss.tvm.apache.org/t/tvm-community-meeting-november-18-2021/11475/4)
to respond.
You are receiving this beca
I think that's what @driazati meant. "Removing" CODEOWNERS doesn't mean to
remove but rename that file: https://github.com/apache/tvm/pull/10192
---
[Visit Topic](https://discuss.tvm.apache.org/t/rfc-remove-codeowners/12095/10)
to respond.
You are receiving this because you enabled mailin
I see. All good then :D
---
[Visit Topic](https://discuss.tvm.apache.org/t/rfc-remove-codeowners/12095/11)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](https://discuss.tvm.apache.org/email/unsubscribe/e723fbd60a6
Thanks for @driazati @areusch to bring this for discussion, I think it make
sense to reduce the notification spam by rename the codeowner file, and
definitely that can help contributor to focus on more related message from
community.
I agree with @comaniac @manupa-arm about helping the new
@areusch:
Yes, using one or two zoom sessions to go over some questions of yours and some
questions of ours will definitely be very, very helpful. This way we can sync
up quicker.
I am open tomorrow (2/25) as well as Monday (2/28) in the afternoons from 1:30
pm to 6 pm Pacific time zone.
Will yo
Long story short, after https://github.com/apache/tvm/pull/8509 we see a lot of
floating point models crash during compilation for Hexagon. On Hexagon
(downstream) we use the mixed-precision pass to convert float32 data to
float16. Float16 constants are not supported by constants in TIR and
Agree with your last sentence -- FoldConstants should be CPU only and not carry
forward any target-specific flags. (Ideally do all that more directly instead
of piggy-backing on the interpreter, but that's a bigger issue.)
---
[Visit
Topic](https://discuss.tvm.apache.org/t/problem-with-fu
I wonder why TIR constants doesn't support fp16? Because of the need for
c-codegen? @manupa-arm
---
[Visit
Topic](https://discuss.tvm.apache.org/t/problem-with-fuseops-and-embedded-constants-in-tir/12165/3)
to respond.
You are receiving this because you enabled mailing list mode.
To uns
I'm not sure. But I guess it is because C++ doesn't have a native fp16 type
support?
---
[Visit
Topic](https://discuss.tvm.apache.org/t/problem-with-fuseops-and-embedded-constants-in-tir/12165/4)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe fr
14 matches
Mail list logo
