[Apache TVM Discuss] [Development] Make binary distributation

Yes, @tqchen and I will post a RFC soon for the binary distribution. --- [Visit Topic](https://discuss.tvm.apache.org/t/make-binary-distributation/7867/4) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://dis

[Apache TVM Discuss] [Development/RFC] [RFC] tlcpack: Thirdparty Binary Packages

So far we only released source code in past tvm releases, and we will continue to do so. As we continue to develop tvm, we also see some demand for convenient binary packages, such as wheel or docker binaries. One important factor of such binary packages is the potential links with third part

[Apache TVM Discuss] [Development/RFC] [RFC] tlcpack: Thirdparty Binary Packages

The wheels are built on a newer version of CentOS. Pip wheel for CPU is manylinux2010 compatibility and wheels for CUDA are manylinux2014 compatibility. Releasing wheels with different CUDA versions is to accommodate different develop and deploy environment. --- [Visit Topic](https://dis

[Apache TVM Discuss] [Development] Remove extra reshape

Sure, I think you can add this into the `SimplifyExpr` pass. I thought about this before, but I think that the reshape op might be inlined in the fused op. --- [Visit Topic](https://discuss.tvm.apache.org/t/remove-extra-reshape/8212/2) to respond. You are receiving this because you enable

[Apache TVM Discuss] [Development/RFC] [RFC] A general task extraction mechanism for auto_scheduler

I have one question about `use_topi_schedule`. I assume that after we set it to False, it will always use the Ansor scheduler to schedule the ops. Will there be a case that we want have a mix of topi schedule and ansor schedule? --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-a-gen

[Apache TVM Discuss] [Development/RFC] [RFC] Rename TVMContext to TVMDevice

I propose to rename the `TVMContext` to `TVMDevice`. Currently, `TVMContext` is used to represent a device that the model is executed on. Two main reasons for this change: 1. the name of `TVMContext` doesn't intuitively reflect its semantics of a device. 2. mainstream frameworks including [

[Apache TVM Discuss] [Development/RFC] [RFC] Rename TVMContext to TVMDevice

1. TVM uses [RPCSession](https://tvm.apache.org/docs/api/python/rpc.html#tvm.rpc.RPCSession.context) to create a remote context/device. We can also change this API to `device`. 2. In fact, I also plan to create a RFC to dlpack for the context name change. --- [Visit Topic](https://discuss

[Apache TVM Discuss] [Development/RFC] [RFC] Rename TVMContext to TVMDevice

I don't know much about µTVM. Need to take a look to comment on this. I think we can make the change in TVM first and change again after the change is pushed to DLPack. Because there'll be more dependencies in DLPack, it'll probably take longer time to change in DLPack. You can also check out

[Apache TVM Discuss] [Development/RFC] [RFC] Rename TVMContext to TVMDevice

I think we can keep `TVMDevice` in the C++ and backend, but use `tvm.device` in the python frontend. It can reduce the confusion when integrating TVM into other frameworks if we keep `TVM` prefix. --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-rename-tvmcontext-to-tvmdevice/9090/1

[Apache TVM Discuss] [Development/RFC] [RFC] Rename TVMContext to TVMDevice

Since everyone agree on A0, I'll go ahead and prepare the PR in next week. --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-rename-tvmcontext-to-tvmdevice/9090/27) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click he

[Apache TVM Discuss] [Development/RFC] [RFC] API change: asnumpy -> numpy

As per discussion, I will prepare the PR to change the API to `numpy` and add a deprecation warning message in the `asnumpy`. --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-api-change-asnumpy-numpy/9846/9) to respond. You are receiving this because you enabled mailing list mode.