author | Ajay Jayaraj <ajayj@ti.com> | |
Fri, 17 Aug 2018 20:14:15 +0000 (15:14 -0500) | ||
committer | Ajay Jayaraj <ajayj@ti.com> | |
Tue, 21 Aug 2018 18:32:28 +0000 (13:32 -0500) | ||
commit | 1b809f0e67c15437d492c5261d654206d6407167 | |
tree | 1002d079212738db3ea252b34323c16176a6933a | tree | snapshot (tar.xz tar.gz zip) |
parent | 1a42784dc57d81735218ec2dc85172a1ed4e8181 | commit | diff |
Report memory usage when device allocation fails
TIDL API creates 2 device side heaps:
1. Parameter heap
2. Network heap
The sizes of these heaps are specified in the Configuration object, via
PARAM_HEAP_SIZE and NETWORK_HEAP_SIZE.
Existing behavior: If the heaps are not large enough, allocation on the
device triggers an assertion failure with no indication of how large the
heaps need to be for successfull allocation.
To improve the usability of the API, provide feedback to the user on the
heap sizes required to satisfy device side allocations when any
allocation fails.
Also added `-Wall -Werror` when building examples and fixed failures.
(MCT-1035)
TIDL API creates 2 device side heaps:
1. Parameter heap
2. Network heap
The sizes of these heaps are specified in the Configuration object, via
PARAM_HEAP_SIZE and NETWORK_HEAP_SIZE.
Existing behavior: If the heaps are not large enough, allocation on the
device triggers an assertion failure with no indication of how large the
heaps need to be for successfull allocation.
To improve the usability of the API, provide feedback to the user on the
heap sizes required to satisfy device side allocations when any
allocation fails.
Also added `-Wall -Werror` when building examples and fixed failures.
(MCT-1035)
19 files changed: