> > We need to add `in_dtype` in the dequantize op as the calculations will be
> > different, especially the range to use.
>
> Guess the input tensor has such information already?
@jackwish, the input data is generally an `Expr` can be `Var` or `IntImm` or
some other type of `Expr`. How will i
I have the same problem. Can it be solved now?
---
[Visit Topic](https://discuss.tvm.ai/t/how-to-support-tf-tensorarray/1983/2) to
respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](https://discuss.tvm.ai/email/unsubscrib
[quote="hjiang, post:13, topic:2987"]
#1. When doing test_vta_insn.py I saw some test case get failed like “ALU MAX
imm:False test took 1654 clock cycles”,
could i know what is this ‘False’ means?
[/quote]
Check the print-message-code, the alu tests uses "immediate" as boolean. So,
False means
@vegaluis, @Ravenwater, I just tried the tsim and want to share my experience
at this same thread,
I tried test_vta_insn.py and Sample Matrix-multiply and resetnet18 tutorial,
the clock cycles measurement seems like awesome, but i also experienced couple
crash and have following questions.
@ajtulloch indeed. However, it will always be possible that ppl might
uncarefully create strong reference loop, and be unable to collect.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/dmlc/tvm/issues/34
cc @hlu1 re: the leak from e.g. recursive functions taking a reference to
itself in the environment.
FWIW, can we solve these via adding the concept of weak references to the node
system? It seems like in these cases that closures could use weak references to
other closures, and have the higher
