@areusch > whether constant data should become a PrimExpr and how much that impacts TIR > parsing time?
Because the scope of the RFC is more like generic constant nodes in TIR, I would say the size could be as large as weights in NN, which can be MBs or even more. Parsing these large weights are generally super slow and thus we should support saving them in separate files. > we will need to find a TIR expression that can do this Yeah I agree, and it can be simpler: as long as it is a packed function in the global registry, we can use `tir.call_packed` to make cross-device transfer possible. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/22#issuecomment-924619408
