tqchen edited a comment on pull request #23: URL: https://github.com/apache/tvm-rfcs/pull/23#issuecomment-925354280
There is generally tradeoffs between: - A0: The desire to preserve information during transformation. - A1: A growing set of attributes that is impossible to keep track of(thus preserve) during transformations. From the A1's pov, allowing set of attributes that changes the semantics of the IR is in general not desirable. Since other pass writers may not be aware of all the possible set of attributes and thus being mindful in preserving them. The middle ground that we could reach here is to allow annotations, which only served as hints for future passes(that the code can be transformed in certain way). This means that the other pass writers can safely ignore the content of annotation itself. Note that this would certainly restrict the possible set of annotations that we can use(e.g. the object themselves should not refer to an active piece in the IR). -- 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]
