[Apache TVM Discuss] [Development] Target Specific Transform Parameters
I have some changes to the loop vectorizer that are target specific. I can plumb a control knob through PassContext but preferably it would be driven by a target attribute. Is there a place that default values for PassContext config values can be specified using the target? The target does not seem to be passed directly into CreatePassList called by LowerModule. --- [Visit Topic](https://discuss.tvm.apache.org/t/target-specific-transform-parameters/10659/1) 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/2573adfa4089647b711efb91f402758c2531cdc741b47fe8ec0e3985fd0d9078).
[apache/tvm] [RFC][Tracking Issue] Additional Target Hooks (#8589)
1. [ ] Add hook for relay_to_tir - https://github.com/apache/tvm/pull/8423 1. [ ] Add hook for tir_to_runtime - 1. [ ] Migrate `relay.ext` to relay_to_runtime / constant_updater - 1. [ ] Migrate external codegen -> target conversion - -- 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/issues/8589
[Apache TVM Discuss] [Development] Why is PrimFunc.buffer_map cleared in MakePackedAPI
There is a benefit of having the association between a `Var` and the corresponding `Buffer` throughout the optimizations, including codegen. `Buffer` is not a `PrimExpr`, so it cannot be passed around directly, but it contains a lot of useful information (such as shape etc.). If we had the `buffer_var -> Buffer` mapping, we could rely on that to associate any `Var` with its buffer (if there is any). However, the `buffer_map` is cleared in `MakePackedAPI`, and the LLVM codegen expects it to be empty. What are the reasons for not having it? Can we keep it? --- [Visit Topic](https://discuss.tvm.apache.org/t/why-is-primfunc-buffer-map-cleared-in-makepackedapi/10663/1) 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/a881e470ec67b1c183b4386b0a138e2ac68e0f61aec912e22b9dd7586dce0ccd).
[Apache TVM Discuss] [Development/pre-RFC] [pre-RFC] Vectorized TIR Buffers
@masahi Tagging following comments on https://github.com/apache/tvm/pull/8528#pullrequestreview-718506978 --- [Visit Topic](https://discuss.tvm.apache.org/t/pre-rfc-vectorized-tir-buffers/10615/5) 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/2b20409dd28ff339a6a9b23c17ad88ce918e6a63561c0b46db2304e8981c9bfc).
[apache/tvm] [RFC] Tracking bug for RFC 0008: microTVM Project API (#8595)
See https://github.com/apache/tvm-rfcs/pull/0008 -- 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/issues/8595
Re: [apache/tvm-rfcs] Add Project API RFC (#8)
@Mousius @tqchen please take a look -- 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/8#issuecomment-889484620
[apache/tvm] [RFC][Tracking Issue] Pipeline Executor For Compute graph pipeline (#8596)
PR https://github.com/apache/tvm/pull/7892 Discussion https://discuss.tvm.apache.org/t/rfc-compute-graph-pipeline-with-new-subgraph-executor/9839/ -- 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/issues/8596
Re: [apache/tvm-rfcs] Add Project API RFC (#8)
@Mousius @mehrdadh @tkonolige @guberti please take another look and https://tvm.apache.org/docs/contribute/code_review.html#approve-and-request-changes-explicitly -- 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/8#issuecomment-889514132
[Apache TVM Discuss] [Development] Why is PrimFunc.buffer_map cleared in MakePackedAPI
The main reason is that buffer map represented a specific semantics of variable defs(eg the vars in the buffer). MakePackedAPI desugars that into a low level form that uses load and intrinsics to define those vars. As a result, the buffer map information can now be stale(or duplicated with the desugared impl). I would try to defer MakePackedAPI as late as possible and do most of the transformations before that, which allows us to take benefit of the high level mapping info. --- [Visit Topic](https://discuss.tvm.apache.org/t/why-is-primfunc-buffer-map-cleared-in-makepackedapi/10663/2) 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/cda0fa90e8851bf0173b35c0dc0cd829317696864a726bba92c21847451d0303).
