[GitHub] [incubator-tvm] wpan11nv edited a comment on pull request #5382: [TE] Fix MakeLoopNest for warp memory

2020-04-27 Thread GitBox
wpan11nv edited a comment on pull request #5382: URL: https://github.com/apache/incubator-tvm/pull/5382#issuecomment-620140371 > Do you mean requiring the users to tag the iter_var or we do it in InferBound? If the former, maybe we can merge this PR first and then start an RFC for the API

[GitHub] [incubator-tvm] wpan11nv edited a comment on pull request #5382: [TE] Fix MakeLoopNest for warp memory

2020-04-24 Thread GitBox
wpan11nv edited a comment on pull request #5382: URL: https://github.com/apache/incubator-tvm/pull/5382#issuecomment-619201349 Can we make it explicit, e.g by tagging the binding iter_var with "warp" scope. For CUDA, when the block configuration is (1, 32), threadIdx.y may be the thread

[GitHub] [incubator-tvm] wpan11nv edited a comment on pull request #5382: [TE] Fix MakeLoopNest for warp memory

2020-04-24 Thread GitBox
wpan11nv edited a comment on pull request #5382: URL: https://github.com/apache/incubator-tvm/pull/5382#issuecomment-619201349 Can we make it explicit, e.g by tagging the binding iter_var with "warp" scope. For CUDA, when the block configuration is (1, 32), threadIdx.y may "define" the