It would be nice if ComputeException (and any other fairly generic exceptions) would add the error code name to the ToString. And if the name isn't available, at least the error code.
Note to self:
1) Hook the cl context notifier which (in theory at least) is given more information than just a simple error code.
2) Append this error info to the appriopriate compute exception and throw it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After some experimenting, I''m forced to classify my own suggestion as unfeasible. So, I've decided to at least insert the error code into the exception message as requested. For the moment that's as much info as one can get from the OpenCL.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually probably adding it to the exception message would be better than overriding ToString.
This is a brilliant idea!
Note to self:
1) Hook the cl context notifier which (in theory at least) is given more information than just a simple error code.
2) Append this error info to the appriopriate compute exception and throw it.
After some experimenting, I''m forced to classify my own suggestion as unfeasible. So, I've decided to at least insert the error code into the exception message as requested. For the moment that's as much info as one can get from the OpenCL.
Reopening feature request.
The exception message can be extended with information from the "Errors" section of the OpenCL man pages.