[TVM Discuss] [Questions] Why does VTA build has its own path?

[JC Li via TVM Discuss <no...@discuss.tvm.ai>]

This is very confusing while I started reading the TVM source code, trying to figure out the build paths. 

Normal build flow seems using **tvm/python/tvm/relay/build_module.py**, which itself is a wrapper for C++ implementations under the hood, such as **tvm/src/relay/backend/build_module.cc** and **tvm/src/relay/backend/compile_engine.cc**. 

However, I just realized VTA build has its own path from **tvm/python/tvm/driver/build_module.py**. This interface calls into **tvm/vta/python/vta/...** python files. VTA bulid is drastically different from main TVM modules. 

Why can't it use the standard build path?





---
[Visit Topic](https://discuss.tvm.ai/t/why-does-vta-build-has-its-own-path/6259/1) to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/e0757de87fa5de4ca6a8d5a8b5233828d737e83fc04300a86bdcd760e0b93bc4).

[TVM Discuss] [Questions] [Resolved] Why does VTA build has its own path?

[JC Li via TVM Discuss <no...@discuss.tvm.ai>]

Ah, I get it. 

All compiling process starts with relay will call into relay.build(...), which will go through what I called the "normal build flow that starts with high-level optimizations. The process is followed up with low level optimizations mainly at TOPI level. 

The VTA calls vta.build() started with TOPI level optimization, thus it started with lower level optimization directly w/o the relay paths above. 

It is recommended we can modify the python files names, maybe.  
**tvm/python/tvm/relay/build_module.py** --> build_relay_modules.py
**tvm/python/tvm/driver/build_module.py** --> build_topi_modules.py

I now marked it as solved. Please correct me if there's anything wrong.





---
[Visit Topic](https://discuss.tvm.ai/t/resolved-why-does-vta-build-has-its-own-path/6259/3) to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/5d7c5d71ba97275130818920b537413ae247a5488b6bb4d9051eb6192535f59a).

[TVM Discuss] [Questions] [Resolved] Why does VTA build has its own path?

[JC Li via TVM Discuss <no...@discuss.tvm.ai>]

I see a path on tvm normal build path side: 

**tvm/python/tvm/relay/build_module.py** -->
**tvm/src/relay/backend/build_module.cc** Lower(...)--> LowerInternal(...) --> 
**tvm/python/tvm/relay/backend/_backend.py** lower(...) -->
**tvm/python/tvm/driver/build_module.py** lower(...)

The last one merges with VTA lower calls.





---
[Visit Topic](https://discuss.tvm.ai/t/resolved-why-does-vta-build-has-its-own-path/6259/2) to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/b23ba2a242b462ff7fd0931ff901ee2b418a61cdf33446e5207420884d9af802).