topic ippsFind bug in Intel® Integrated Performance Primitives

ippsFind bug

OTorg — Thu, 22 Sep 2011 07:20:03 GMT

__declspec( align(16) ) BYTE pbmem[32] = {

0x55, 0x55, 0x55, 0x55, 0x55, 0x55, 0x55, 0x55,

0x55, 0x55, 0x55, 0x55, 0x00, 0x55, 0x55, 0x55,

0x55, 0x00, 0x00, 0x01, 0xBA, 0x55, 0x55, 0x55

};

BYTE pbcmp[ 4 ] = { 0x00, 0x00, 0x01, 0xBA };

int Index;

ippsFind_8u( pbmem, 27, pbcmp, 4, &Index );

returns Index = 25, but a correct answer is -1 (25+4=29 > 27 - points to out of range memory)

tested onCore2 Quad Q9300,Core i7 870

ippcore-7.0.dll version: 7,0,205,1015

ippsFind bug

Gennady_F_Intel — Fri, 23 Sep 2011 13:38:37 GMT

I didn't reproduce the issue:

Checked with 7.0 update 5:

ippsv8-7.0.dll 7.0 build 205.58 7.0.205.1058

Index == -1

ippsFind bug

OTorg — Sat, 24 Sep 2011 11:57:52 GMT

I have renewed ipp to 7.0 update 5, ippGetLibVersion() returns: 7.0 build 205.68; 7.0.205.1032.

And also check on the older computer.

Got the following results (x86):

25 on Core2 Quad Q9300 (ippchp8-7.0.dll)

25 on Core i7 860 (ippchp8-7.0.dll)

-1 on Pentium 4 630 (ippchw7-7.0.dll)

code:

__declspec( align(64) ) BYTE pbmem[32] = {

0x55, 0x55, 0x55, 0x55, 0x55, 0x55, 0x55, 0x55,

0x55, 0x55, 0x55, 0x55, 0x00, 0x55, 0x55, 0x55,

0x55, 0x00, 0x00, 0x01, 0xBA, 0x55, 0x55, 0x55

};

__declspec( align(64) ) BYTE pbcmp[ 4 ] = { 0x00, 0x00, 0x01, 0xBA };

int Index;

ippsFind_8u( pbmem, 27, pbcmp, 4, &Index );

ippsFind bug

Gennady_F_Intel — Sun, 25 Sep 2011 04:37:04 GMT

Ok, I will check on i7 system. it looks like the next problem with dispatching code.

ippsFind bug

Gennady_F_Intel — Sun, 25 Sep 2011 05:50:30 GMT

the issue is reproduced on SNB system:

ippsg9-7.0.dll 7.0 build 205.68 7.0.205.1067

Index == 25

Here is a bug tracking number for your reference:

DPD200169895.

I will inform you once a new update becomes available.

--Gennady

ippsFind bug

OTorg — Mon, 26 Sep 2011 06:44:59 GMT

Ok. Thanks!

Can you take a look on a one more problem:software.intel.com/en-us/forums/showthread.php?t=86463

This is probably not applicable to your area of responsibility, but nobody answers mein the forum "AVX and CPU Instrutstions".