1. You are right, we actually tried to save the runtime.Module. We actually also added the TIR export to the runtime.Module because the generated source code is also put to it. We will try the different options you proposed as soon as we can find the time. 2. In the meantime we have written an early prototype of our export. I attached a small sample image of what it looks like, compared to what save_json gives for the same IRModule. I do not think that save_json gives us the required level of detail but to be honest, I did not look at it in great detail.
  3. We did not yet look into this, sorry 4. As you can probably see, we want to extract TIR just before the code generator is invoked. We would like to get all the details that also go into the final code generation step. 5. We want to make this useful for as many use cases as possible, so if we can make the point in time of the export configurable, we are definitely in favor of doing so. I am not sure however, how much this will affect the implementation of the TIR export printer. It might then possibly need configuration options as well, right? --- [Visit Topic](https://discuss.tvm.apache.org/t/export-tir-to-json/12329/7) 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/c34f12263ea2c2c94ded8aebd5c47c9e0db77f4e83ee06fc1443dfe1f2087864).
