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
   # ...
   ```

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/70#issuecomment-1123341991
You are receiving this because you are subscribed to this thread.

Message ID: <apache/tvm-rfcs/pull/70/c1123341...@github.com>

Reply via email to