That should be doable as well. I think that should be a `Block(prologue, For, epilogue)` though, as we still want the loop, not just the body.
However, I'm wondering if this would become a common pattern used for many targets. So far, non-trivial accelerators with the [RoCC interface](https://inst.eecs.berkeley.edu/~cs250/sp17/disc/lab2-disc.pdf) would require this pattern to ensure memory consistency, and I'm anticipating that more heterogeneous SoCs may benefit from this pattern, not just for memory consistency (e.g. enabling a power-hungry device prior to computation and disabling it afterwards). --- [Visit Topic](https://discuss.tvm.ai/t/add-support-for-extern-prologue-epilogue-functions/6041/6) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/7c36bf268ebedb15a7a1691a288f06f925d06a4766a7e21ba98d0bbd5fbf6299).
