ioc32 build failure

[Albert_Y_]

ioc32.exe (6.3.0.1904) exited with code -1073741819 (0xc0000005) and a stack dump when compiling surf.cl from OpenCV 2.4.x.
See the attached log file.
Platform is VS 2013 on Windows 10.

I narrowed the failure to the following section of code in icvCalcOrientation.

if (tid < ORI_SAMPLES)
{
        const float margin = (float)(grad_wav_size - 1) / 2.0f;
        const int x = convert_int_rte(featureX[get_group_id(0)] + c_aptX[tid] * s - margin);
        const int y = convert_int_rte(featureY[get_group_id(0)] + c_aptY[tid] * s - margin);

        if (y >= 0 && y < (c_img_rows + 1) - grad_wav_size &&
                x >= 0 && x < (c_img_cols + 1) - grad_wav_size)
        {
                X = icvCalcHaarPatternSum_2(sumTex, c_NX, 4, grad_wav_size, y, x, c_img_rows, c_img_cols, sum_step);
                X = c_aptW[tid] * X;
                Y = icvCalcHaarPatternSum_2(sumTex, c_NY, 4, grad_wav_size, y, x, c_img_rows, c_img_cols, sum_step);
                Y = c_aptW[tid] * Y;
                angle = atan2(Y, X);

If you swtich lines 11 and 12 in this snippet, the code will compile.

[Jeffrey_M_Intel1]

I've tried replicating on several machines.  So far I have not been able to see this behavior.  Could you let me know a little bit more about your environment?  Some details which could be important are processor and graphics driver version.

[Albert_Y_]

My compile-time environment is a VMWare virtual machine. The only platform that the tools are able to target is the CPU. Perhaps that is why it is different from  your test environments.

Platform names:
    [0] Experimental OpenCL 2.1 CPU Only Platform [Selected]
Number of devices available for each type:
    CL_DEVICE_TYPE_CPU: 1
    CL_DEVICE_TYPE_GPU: 0
    CL_DEVICE_TYPE_ACCELERATOR: 0

*** Detailed information for each device ***

CL_DEVICE_TYPE_CPU[0]
    CL_DEVICE_NAME: Intel(R) Core(TM) i5-4570S CPU @ 2.90GHz
    CL_DEVICE_AVAILABLE: 1
    CL_DEVICE_VENDOR: Intel(R) Corporation
    CL_DEVICE_PROFILE: FULL_PROFILE
    CL_DEVICE_VERSION: OpenCL 2.1 (Build 18)
    CL_DRIVER_VERSION: 6.3.0.1904
    CL_DEVICE_OPENCL_C_VERSION: OpenCL C 2.0
    CL_DEVICE_MAX_COMPUTE_UNITS: 2
    CL_DEVICE_MAX_CLOCK_FREQUENCY: 2900
    CL_DEVICE_MAX_WORK_GROUP_SIZE: 8192
    CL_DEVICE_ADDRESS_BITS: 32
    CL_DEVICE_MEM_BASE_ADDR_ALIGN: 1024
    CL_DEVICE_MAX_MEM_ALLOC_SIZE: 536838144
    CL_DEVICE_GLOBAL_MEM_SIZE: 536838144
    CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE: 131072
    CL_DEVICE_GLOBAL_MEM_CACHE_SIZE: 262144
    CL_DEVICE_GLOBAL_MEM_CACHELINE_SIZE: 64
    CL_DEVICE_LOCAL_MEM_SIZE: 32768
    CL_DEVICE_PROFILING_TIMER_RESOLUTION: 353
    CL_DEVICE_IMAGE_SUPPORT: 1
    CL_DEVICE_ERROR_CORRECTION_SUPPORT: 0
    CL_DEVICE_HOST_UNIFIED_MEMORY: 1
    CL_DEVICE_EXTENSIONS: cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_depth_images cl_khr_3d_image_writes cl_intel_exec_by_local_thread cl_khr_spir cl_khr_dx9_media_sharing cl_intel_dx9_media_sharing cl_khr_d3d11_sharing cl_khr_gl_sharing cl_khr_fp64 cl_khr_image2d_from_buffer
    CL_DEVICE_PREFERRED_VECTOR_WIDTH_INT: 1
    CL_DEVICE_PREFERRED_VECTOR_WIDTH_LONG: 1
    CL_DEVICE_PREFERRED_VECTOR_WIDTH_FLOAT: 1
    CL_DEVICE_PREFERRED_VECTOR_WIDTH_DOUBLE: 1
    CL_DEVICE_NATIVE_VECTOR_WIDTH_INT: 4
    CL_DEVICE_NATIVE_VECTOR_WIDTH_LONG: 2
    CL_DEVICE_NATIVE_VECTOR_WIDTH_FLOAT: 8
    CL_DEVICE_NATIVE_VECTOR_WIDTH_DOUBLE: 4

[Jeffrey_M_Intel1]

Thanks for the additional info.  I've replicated and filed as a bug.  BTW the CPU target device (not CPU_2_1) seems to work without issue.  Is this an option for you?

[Albert_Y_]

Yes, the CPU driver works.  I hadn't tried it before because I didn't realize that is was a separate download.