You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tvm.apache.org by GitBox <gi...@apache.org> on 2022/05/11 08:25:14 UTC

[GitHub] [tvm-rfcs] wrongtest commented on pull request #70: [RFC] Introducing DeclBuffer

wrongtest commented on PR #70:
URL: https://github.com/apache/tvm-rfcs/pull/70#issuecomment-1123341991

   Thanks a lot!  I think then we can handle buffer related issues in customized passes with more explicit and robust way.
   
   I have one question on tir script, for certain algorithms in DL workloads, users may want to write non-stir formed script like
     ```python
     x = T.allocate((), "int32", "")
     x[()] = 0
     while x[()] < 128:
         x[()] = x[()] + 1
         # ...
     ```
      Could the parser support still write things like that (though underlying IR structure changed) instead of
      ```python
      x_data = T.allocate((), "int32", "")
      x = T.decl_buffer(data=x_data,)
      x[()] = 0
      # ...
      ```


-- 
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: commits-unsubscribe@tvm.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org