cancel
Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

psamathos
Journeyman III

Crash when using vector pointers as kernel arguments

Hi,

I have a kernel where I process blocks of 16 uchar/ushort and since OpenCL has a ushort16 type I thought it would be great to use those. However the kernel crashes, which I find odd since it works with Intel's OpenCL. It also works if I use vstore16/vload16, the memory is aligned on 4k-boundaries, it's only on the cpu. Using ushort8/uchar8 seems to work.

Have I misunderstood something or is this a bug?

Two simple kernels

kernel void thisOneCrashes(global const uchar16* data1, global ushort16* data2)

{

          data2[0] = (ushort16)(1);

}

kernel void thisOneDoesnt(global const uchar* data1, global ushort* data2)

{

          vstore16((ushort16)(1), 0, data2);

}

regards

Magnus Sjöstrand

Tags (1)
0 Likes
1 Reply
binying
Challenger

Re: Crash when using vector pointers as kernel arguments

The simple test kernel works fine on my machine.

__kernel void test (__global ushort16* in)

{

in[0] = (ushort16)(1);

}

I am using the latest driver & sdk on HD6990. I hope this will be helpful for you. 

0 Likes