| author | Yuan Zhao <yuanzhao@ti.com> | |
| Mon, 10 Jun 2019 20:12:03 +0000 (15:12 -0500) | ||
| committer | Yuan Zhao <yuanzhao@ti.com> | |
| Mon, 10 Jun 2019 20:12:03 +0000 (15:12 -0500) | ||
| commit | 2fca00418b2bf5849255b7dd87deb31f95c36f1a | |
| tree | 69daf84f93324ea10470c0dcb371d024fad386a6 | tree | snapshot (tar.xz tar.gz zip) |
| parent | 923d5b51a031a723c6db60c436cd1f430333e78d | commit | diff |
Fix unique_ptr that holds an allocated array
- Customer reported this problem. unique_ptr that holds an allocated
array was created as "unique_ptr<char>", which will call "delete"
at destruction. However, the array was created with "new char[]".
The proper way should be "unique_ptr<char[]>", so that "delete []"
will be called at destrution.
- One minor trace message update so that we know which type of device
is being dispatched to.
- MCT-1196
- Customer reported this problem. unique_ptr that holds an allocated
array was created as "unique_ptr<char>", which will call "delete"
at destruction. However, the array was created with "new char[]".
The proper way should be "unique_ptr<char[]>", so that "delete []"
will be called at destrution.
- One minor trace message update so that we know which type of device
is being dispatched to.
- MCT-1196
| tidl_api/src/ocl_device.cpp | diff | blob | history |