topic Thanks for the follow-up. in Intel® Integrated Performance Primitives

ippiFilterBorder_32f_C1R with ipp16s kernel

Patrick_H_3 — Sun, 03 Dec 2017 22:57:04 GMT

Is this combination supposed to work? It appears that this border filter results in memory corruption if the kernel specified is 16s rather than 32f (in ippiFilterBorderInit_16s rather than ippiFilterBorderInit_32f). Other pixel types (e.g., 16u, 16s, 8u) work with both types of kernel, but the 32f pixel type appears to operate correctly only with a 32f kernel. The workaround is easy enough (i.e., use a float kernel for float pixels), but the documentation and return code do not indicate that the 16s kernel is not supported for 32f pixels. This is with the 2018 update 1 version of IPP.

Hello,

Alice_H_Intel — Tue, 05 Dec 2017 04:07:26 GMT

Hello,

I'll investigate this and get back to you soon.

Thanks,

Alice

Hi Patrick.

Andrey_B_Intel — Tue, 05 Dec 2017 22:52:38 GMT

Hi Patrick.

ippiFilterBorder_32f_C1R with ipp16s kernel is not supported because internal implementation uses float data type. We add BadStatus in next IPP release.

Thanks.

Thanks for the follow-up.

Patrick_H_3 — Tue, 05 Dec 2017 23:07:32 GMT

Thanks for the follow-up. That is what I had guessed.