[TVM Discuss] [RFC] Introducing Hexagon backend

2019-08-13 Thread Hawk Zhou via TVM Discuss
I think if adding copyonright within hexagon code or not will not be a problem cause that these code will only used on Qualcomm soc. --- [Visit Topic](https://discuss.tvm.ai/t/introducing-hexagon-backend/2421/19) to respond. You are receiving this because you enabled mailing list mode. T

[TVM Discuss] [RFC] Introducing Hexagon backend

2019-07-02 Thread Krzysztof Parzyszek via TVM Discuss
The special runtimes are mostly for offloading to extra devices from host. ARM and X86 are usually the hosts, so the runtime for them is fairly simple. It's still there, look at cpu_device_api.cc for example. --- [Visit Topic](https://discuss.tvm.ai/t/introducing-hexagon-backend/2421/18)

[TVM Discuss] [RFC] Introducing Hexagon backend

2019-07-01 Thread Lan Tn via TVM Discuss
My current problem is that I don't see special X86 or ARM support in the runtime's code. --- [Visit Topic](https://discuss.tvm.ai/t/introducing-hexagon-backend/2421/17) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click her

[TVM Discuss] [RFC] Introducing Hexagon backend

2019-05-02 Thread Zhao Wu via TVM Discuss
However, in GetTempAllocaAlignment function, it will reduce alignment / 2 in while loop. I am worried about this will affect DSP’s rule, it requires 128 bits alignment. --- [Visit Topic](https://discuss.tvm.ai/t/introducing-hexagon-backend/2421/7) to respond. You are receiving this becau