[apache/tvm-rfcs] [RFC] Markdown for CMSIS-NN integration (#15)

This RFC details integration of CMSIS-NN API into TVM to support code generation for Arm(R) Cortex-M using the following library: https://github.com/ARM-software/CMSIS_5/tree/develop/CMSIS/NN cc : @areusch @mbaret @tqchen You can view, comment on, or merge this pull request online at: http

Re: [apache/tvm-rfcs] Update the guideline of RFC tracking issues (#13)

Merged #13 into main. -- 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/13#event-5107036807

Re: [apache/tvm-rfcs] [RFC] Markdown for CMSIS-NN integration (#15)

Minor nit - the title of the RFC should really read - [RFC] Use CMSIS-NN with TVM. @manupa-arm , @Mousius .. -- 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/15#issuecomment-892150107

Re: [apache/tvm-rfcs] Additional Target Hooks RFC (#10)

Hi @jroesch, It'd be great to discuss this further, as there's some interesting points you've raised. > The lowering process should be a straight forward mapping from TE -> TIR, and > then any necessary customization should be possible in resulting passes which > are allowed to view the entire

Re: [apache/tvm] [RFC][Tracking Issue][AMP] Tracking Issue for Mixed Precision Pass (#8296)

I've hit a nasty issue. On CPU targets, our sorting related ops are implemented in C++ https://github.com/apache/tvm/blob/main/src/runtime/contrib/sort/sort.cc#L436, and they don't support fp16. So ops like `topk`, `argsort`, `nms` etc do not work on fp16 + cpu target combination. We can add al