@masahi Yes, exactly, but it looks like TVM doesn't support it, does it?
I'm thinking of a temporary workaround by adding appending all the constraints
and axis dependencies as well as a function to verify a config's validity to
the ConfigEntity class. Every time when a tuner's `next_batch` func
In this case it is not polyhedral model, but just some constraints on the
config space.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/5809#issuecomment-650211024
General Comments
IMHO, @merrymercy's comments on log files are valuable. Many users now look
into the log file for the information they need, and even manually modify some
logs for experiments or optimizations. This can be achieved because 1) the log
files are in text format, and 2) one c
Polyhedral analysis would be an approach to generate the constraints in this
scenario. On the other hand, the runtime validation sounds not a general
solution, because it might affect the tuner. For example, throwing invalid
configs in `next_batch` would result in no measurement results for thos
# Bug Fixes
* Fixed process termination routine in windows #4844
* [Runtime] Fix NDArray SaveDLTensor declaration and implementation signature
different #4586
* [NODE][Serialization]fix serialization precision loss in float #4503
* [Relay][Frontend][TF] fix _parse_param bug #4711
* Fix bias_add g
Dear TVM community,
This is a call for vote to release Apache TVM (incubating) version 0.6.1. This
is a maintenance release incorporating important bug fixes. All users of Apache
TVM (incubating) 0.6.0 are advised to upgrade.
Link to release notes:
https://github.com/apache/incubator-tv
> could you be a bit more specific wrt your API design comment?
Sorry, I meant to be consistent with the registry API / implementation defined
at
[src/runtime/registry.cc](https://github.com/apache/incubator-tvm/blob/master/src/runtime/registry.cc).
Specifically, I think it's better to implem
+1 (binding), I checked
- Signatures and hashes good
- DISCLAIMER, LICENSE, NOTICE
- Signatures and hashes
- No unexpected binary files
- Code compiles
TQ
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/
For bare-metal devices, it is desirable (for both space and performance
reasons) to have a network that consists entirely of integral data types (most
often `int8`). However, the automatic integer quantization mechanism in Relay
does not serve this use case for two reasons:
1) Inputs are assu
Ah gotcha. I think there's one thing there I'm not sure how to solve in a good
way: TVM generates TVMBackendPackedCFunc from llvm and c codegens. Because
TVMFuncCall RPC call accepts a function handle, we have to provide something
there that contains enough data to differentiate between TVMBac
+1
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/5939#issuecomment-650468556
+1
Thierry
> On Jun 26, 2020, at 6:16 PM, masahi wrote:
>
> +1
>
> --
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/apache/incubator-tvm/issues/5939#issuecomment-650468556
---
+1
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/5939#issuecomment-650471485
+1
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/5939#issuecomment-650476981
+1
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/5939#issuecomment-650478109
+1
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/5939#issuecomment-650484640
@tqchen @comaniac Thanks for the comments! The feedback of the invalid configs
is something I didn't think of. Actually this is the representation I came up
for non-grid config space. If the config space is too large, and there are too
many constraints so that the shape of the space is very irre
17 matches
Mail list logo
