OpenCL* for CPU
Ask questions and share information on Intel® SDK for OpenCL™ Applications and OpenCL™ implementations for Intel® CPU
Announcements
This forum covers OpenCL* for CPU only. OpenCL* for GPU questions can be asked in the GPU Compute Software forum. Intel® FPGA SDK for OpenCL™ questions can be ask in the FPGA Intel® High Level Design forum.
1663 Discussions

Failed to create profile program: -34 (CL_INVALID_CONTEXT)

allanmac1
Beginner
238 Views

I don't seem to be able to run "Deep Analysis" on my kernel.

It always returns an error: Failed to create profile program: -34 (CL_INVALID_CONTEXT)

I'm running Win7/x64, the latest Beta Intel HD driver and today's new OpenCL 2014 package.

The processor is an HD Graphics Ivy Bridge 6 EU model (Celeron 1037U !!!). :)

0 Kudos
6 Replies
Raghupathi_M_Intel
238 Views

Can you provide more details on how we can reproduce this issue? What is your kernel, how are you setting the inputs etc.?

Raghu

allanmac1
Beginner
238 Views

I can send you a Kernel Builder session that reproduces it.

I've stripped it down to a kernel that loads 8 uint8 vectors and stores 8 uint8 vectors.  

The Kernel Builder input variable is 8 uint8's (randomized) and the output is 8 uint8's (zeroed).

It always fails with a -34 error.

I don't know if this is an issue with the ultra-tiny Celeron 1037U (Ivy Bridge).  

I'm running the latest HD Graphics beta driver (10.18.10.3574).

Oren_S_Intel1
Employee
238 Views

Hi,

 

Can I assume from the other message you wrote (https://software.intel.com/en-us/comment/1790130) that this issue is solved?

 

Thanks,

Oren

allanmac1
Beginner
238 Views

No, that issue wasn't solved.  I emailed a reproducing case to Raghu.  It's the same .kbsess I sent you. 

The issue appears to be related to include files being problematic during Deep Analysis.

Thanks!

allanmac1
Beginner
238 Views

I still get this error on a Haswell HD4600 when loading a new session or launching a Deep Analysis.

Any progress on this bug?

allanmac1
Beginner
238 Views

Huzzah, the bug is gone in today's Inde 2015 Update 2.

Reply