srkreddy1238 commented on PR #17599: URL: https://github.com/apache/tvm/pull/17599#issuecomment-2641978382
Off late realized, I could have drafted an RFC to describe the approach. Have done now https://discuss.tvm.apache.org/t/rfc-annotate-custom-scope-layout-relax-pass-for-adreno-gpu/18052 @tqchen thanks for the thoughts. Few concerns I have in this approach - ``tir.opencl_texture_2d_supported = true`` : I assume this flag will be used to realize VDevice in struct_info after FuseTIR. Then, only flag may not be sufficient here we might need scope information for each input. And this information to be consistent while we pass through the fusion ops. - Another moderate challenge is in ``S2``, where we need to define and maintain BYOC like pattern table to ensure maximum fusion possibilities. Pls advice. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
