Hey all, heads up I'm taking a close look at the 'pass ordering' problem hiding
in this RFC. That is, as written and prototyped, CollageFuseOps runs just
before the current FuseOps so that it can 'see' rewrites which guide TVM's
native fusion rules. However some of those rewrites are target spec
runtime.Module itself is a runtime object, which does not yet support full
serialization(due to the nature of some module not being able to
serialize(e.g. DSO)). There was a discussion about [Artifact
class](https://discuss.tvm.apache.org/t/introduce-artifact-a-container-for-generated-code/11
The recording has been [posted](https://youtu.be/1t2wf-hDjwg).
---
[Visit
Topic](https://discuss.tvm.apache.org/t/next-tvm-community-meeting-march-16/12298/3)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](https:/
We discussed this at the TVM Community Meeting this morning. A couple of notes:
- What is the best reference paper for Relay? Where was the algebra for the
type relations used here sourced from?
Steven: The [Relay paper](https://arxiv.org/abs/1810.00952) is still the
most comprehensive re
Hi,
thanks for the reference to this function. I was not aware of it.
However I tried it on a Module(c) and got this:
`{
"root": 1,
"nodes": [
{
"type_key": ""
},
{
"type_key": "runtime.Module"
}
],
"b64ndarrays": [],
"attrs": {"tvm_version": "0.9.dev0"
It's been deprecated a long time ago. Is it still maintained? If not, I
suggest that we delete it.
---
[Visit Topic](https://discuss.tvm.apache.org/t/should-we-delete-nnvm/12330/1)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these email
@manupa-arm would be great to get your view on this too
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/62#issuecomment-1069262209
You are receiving this because you are subscribed to this thread.
Message ID:
Thanks @SebastianBoblestETAS . TVM already have a reflection based mechanism
to serialize IR nodes (includin TIR and other functions) as [json
format](https://tvm.apache.org/docs/reference/api/python/ir.html?highlight=save_json#tvm.ir.save_json).
So it would be great to see if that functional
> Im wondering whether should we provide an optional partitioning hook as well
> -- so then it can be anything (i.e. any Sequential) and let the default be a
> Sequential of MergeComposite, AnnotateTarget, MergeCompilerRegions,
> ParititionGraph. WDYT ?
Considering how partitioning is handled i
Thanks, @SebastianBoblestETAS. I agree that json is a great format for
serializing, but I have a few questions:
1. What are the pros and cons of json format compared with TVMScript (if we
have python env)
2. How to design a json format to store all TIR information for all possible
nodes? Do
We propose to implement an API to TVM that allows users to export the TIR
representation of the generated kernels as json.
**Motivation**
Json is a standard file format and can easily be processed in python, for
example. A json interface allows to analyze the generated kernels target
agnos
11 matches
Mail list logo
