The main reason is that buffer map represented a specific semantics of variable defs(eg the vars in the buffer).
MakePackedAPI desugars that into a low level form that uses load and intrinsics to define those vars. As a result, the buffer map information can now be stale(or duplicated with the desugared impl). I would try to defer MakePackedAPI as late as possible and do most of the transformations before that, which allows us to take benefit of the high level mapping info. --- [Visit Topic](https://discuss.tvm.apache.org/t/why-is-primfunc-buffer-map-cleared-in-makepackedapi/10663/2) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/cda0fa90e8851bf0173b35c0dc0cd829317696864a726bba92c21847451d0303).
