Yes, I'd very much support a patch to get you going again. I'm confused as to
why just setting the virtual_device_ in the visitor directly does not work, so
option a is you send me a unit test and I dig into that. Option b is your
patch, however since you've needed to bounce back to c++ perhap
Hi Mark, thank you for clarifying.
If I'm not interested in using the virtual_device feature, is there a way to
disable it? The issue is that without the patch above, it is not possible to
use any pass that is based on the ExprMutator in Python, because the TE
Compiler complains with the abov
Hi Rafael, virtual device handling is unfortunately in a halfway-implemented
state, and it's been on my backlog for a while to wrap that up. Sorry about
that! I'm hoping I can work on it in a few weeks as a break between other tasks.
There's a few things to be done:
- Populate the virtual_dev
While switching to TVMC, I noticed a "virtual_device" property on the top-level
relay module function. It was not properly propagated through my relay passes
and caused an assertion in lowering to TE, with:
Check failed: (!virtual_device->IsFullyUnconstrained()) is false
at:
```
File "
