mohitu
November 16, 2018, 1:56am
1
errcode = clEnqueueReadBuffer(clCPUCommandQue, ptrout_mem_objGPU, CL_TRUE, readoffsetGPU, readsizeGPU, ptrout + (int)splittingPoint * DIM_LOCAL_WORK_GROUP_Y * ncols, 0, NULL, NULL);#Error in reading GPU mem
clEnqueueReadBuffer throws CL_INVALID_MEM_OBJECT error. I am not able to find any solution to this.
According to the documentation, the mem. object should have been undeclared. but, it has been declared.
Could someone help me in this?
[QUOTE=mohitu;43966]clEnqueueReadBuffer throws CL_INVALID_MEM_OBJECT error. I am not able to find any solution to this.
Could you please include:
Which device and driver/implementation version are you running on?
What arguments are you passing when the buffer is created?
It’d be great if you could include (snippets of) a log generated by the Intercept Layer for OpenCL Applications with CLInfoLogging and CallLogging enabled, but code snippets could work also:
# How to Use the Intercept Layer for OpenCL Applications
This file is automatically generated using the script `generate_controls_doc.py`.
Please do not edit it manually!
By default, the Intercept Layer for OpenCL Applications will not modify any OpenCL
calls. You may notice some status messages being printed to stderr, but otherwise
your application should run exactly as it does without the Intercept Layer for
OpenCL Applications.
## Controls
The Intercept Layer for OpenCL Applications is controlled using the Windows
registry, Linux configuration files, or environment variables on all OSes.
### Windows Registry
On Windows, the Intercept Layer for OpenCL Applications reads its registry keys
from:
show original
# How to Use the Intercept Layer for OpenCL Applications
This file is automatically generated using the script `generate_controls_doc.py`.
Please do not edit it manually!
By default, the Intercept Layer for OpenCL Applications will not modify any OpenCL
calls. You may notice some status messages being printed to stderr, but otherwise
your application should run exactly as it does without the Intercept Layer for
OpenCL Applications.
## Controls
The Intercept Layer for OpenCL Applications is controlled using the Windows
registry, Linux configuration files, or environment variables on all OSes.
### Windows Registry
On Windows, the Intercept Layer for OpenCL Applications reads its registry keys
from:
show original