The current design of the compile_engine utilises ScheduleGetter to translate a
primitive function into a scheduled tensor expression. However, as it is an
all-in-one pass, this means it is directly coupled to the schedules defined in
TOPI. It would instead be useful to break this into two sta
Hi @tkonolige,
Thanks a lot for your help.
Unfortunately, your fix didn t solve the problem.
I am a bit confused because my implementation is very closed to the one for
conv2d_NCHWc_int8
```
def _schedule_conv2d_NCHWc_int8(cfg, s, output):
conv = output.op.input_tensors[0]
packed_d
Thanks for the RFC! I do agree that it would be great to create an additional
path to improve the flexibility, especially now we have auto_scheduler to
schedule a TE graph from scratch (cc @merrymercy).
Meanwhile, I think tightly-coupled the selection of schedule and compute is
intentional be
> it seems you need to call `lower_call` twice (one in `TETranslator` and
> another in `ScheduleGetter` ). In this case, seems like you still select the
> schedule in `TETranslator`
So yes, I do call it twice and really this is a consequence of 'lower_call'
also probably needing a similar ref
Thanks for clarification and now I feel we are on the same page. For the idea
of StrategySelector, I have no idea for now and would like to know opinions
from other as well.
---
[Visit
Topic](https://discuss.tvm.apache.org/t/rfc-refactor-the-compile-engine-to-expose-a-relay-te-translator/
@kevinthesun Pinging in case you have wondered about this before
---
[Visit
Topic](https://discuss.tvm.apache.org/t/role-of-the-llvm-autovectorizer-in-tvm/8388/2)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](htt
