Document NV error code#927
Conversation
Yes, this is a somewhat generic error and can mean one of many things. A couple of options -
|
|
Does CUDA also only have 1 error code for all possible kernel execution problems? If not, is it possible to improve the NV implementation of OpenCL to reflect different CUDA error codes? |
|
Well, confirmation from someone from NV that the error code is more general - is already great. But I still think it's best to review where this error is thrown and add a few new, more specific enums. |
It feels a bit backward to add like this, but this error code is used in production for a while but isn't defined in XML.
The name
CL_KERNEL_ILLEGAL_BUFFER_READ_WRITE_NV... Seem to not fully describe the situation, I think I've seen it thrown in other cases.The only thing I'm sure about is that this error is only thrown while the kernel is executing (never while compiling/linking).
I think I found this name on some random forum a while ago.
Back then I force-added it to my bindings without thinking, to get human-readable errors while testing my code.
But I can imagine, this would also be useful the same way to others...
Do I need to ping someone from NV?
Also, any naming suggestions?