Intel® Integrated Performance Primitives
Deliberate problems developing high-performance vision, signal, security, and storage applications.
6709 Discussions

ippiBGRToLab_32f_C3R Segfault on non-scaled data

Stephen_K_
Beginner
‎01-14-2015 02:49 PM
286 Views

The BGR to Lab documentation mentions that

 The equations above are given on the assumption that initial B, G, R values are normalized to the range [0..1]. The computed values of the L component are in the range [0..100], a and b component values are in the range [-128..127].

Is this intended to mean that the conversion functions cannot be used if the floating point data does not lie in that range? Either way, these calls on my system using the edition of IPP that shipped with composer_xe_2015.1.133 cause a segmentation fault if the floating point data does not lie in that range.

0 Kudos

Link Copied

1 Reply
Igor_A_Intel
Employee
‎01-20-2015 11:51 PM
286 Views

Hi Stephen,

you are right - the input data MUST be normalized as it is mentioned in the manual. Internal algorithm uses table-based approach - so non-normalized data leads to hits beyond the table boundaries and access violation (segfault) as a result.

regards, Igor

0 Kudos
Copy link
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.