> This aligns with A2.2 -- directly registering each attribute.
@manupa-arm Then just for clarification a few questions because I might have
misunderstood your initial idea. For A2.1 you were thinking about registering
an attribute preprocessor to the target
`Target().add_attrs_preprocessor(Preprocessor)` that would operate on a
predefined attribute (e.g., `-uma_attrs=<string>`) by processing the `<string>`
and creating a Dict/Map from it?
So a user would only write `tvm.target.Target("ultra_trail -uma_attrs=<my
custom attr string>")` and in code you would access the target via
`target.attrs["uma_attrs"]["attr1"]`, `target.attrs["uma_attrs"]["attr2"]`,
ect.?
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/60#issuecomment-1128673299
You are receiving this because you are subscribed to this thread.
Message ID: <apache/tvm-rfcs/pull/60/c1128673...@github.com>
