[GitHub] [tvm] quic-sanirudh commented on pull request #14316: [TensorIR] New schedule primitive `set_dtype`

["quic-sanirudh (via GitHub)" <gi...@apache.org>]

quic-sanirudh commented on PR #14316:
URL: https://github.com/apache/tvm/pull/14316#issuecomment-1472146828

   > It's a bit tricky since it would change the behavior of the PrimFunc (aka get different result before and after the schedule)
   
   There seems to be some interest in introducing schedule primitives like these that might cause different output. This certainly seems like a useful primitive to have, but since we don't normally want schedule primitives to cause the output to change, primitives like these might be hard to introduce.
   
   Would it make sense to have some discussion on perhaps introducing a different scheduling class that allows these kinds of primitives, or explicitly setting a "danger" flag in the Schedule class before using these primitives. That way, we could still allow primitives like these and make sure that a user knows the risk of using a primitive that could cause the output to change.


-- 
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