You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am considering using opencl for my application, and this tool is the closest I found for comfortable kernel debugging...So i'd like to know of this project is still being maintained.
Thanks for any answers.
edit: I intend to write kernels that will ultimately run on GPUs. Can programs debugged using oclgrind be considered safe for such use?
The text was updated successfully, but these errors were encountered:
i'd like to know of this project is still being maintained.
Yes, but it's not as regularly updated as I'd like. I try to keep on top of new bug reports and pull requests but am a little behind at the moment.
I intend to write kernels that will ultimately run on GPUs. Can programs debugged using oclgrind be considered safe for such use?
I'm not sure exactly what you mean by "safe", but Oclgrind can certainly find some of the more common issues that may cause problems on real GPUs (such as out-of-bounds memory accesses and barrier divergence).
I do a lot of OpenCL debugging and oclgrind is completely indispensable. The data race detector (although memory hungry) is also a lifesaver. It may be that oclgrind does not change all that often, but neither does OpenCL. In fact, I often use oclgrind to debug code that will eventually run on CUDA, because I'm not aware of a comparably effective CUDA tool.
I am considering using opencl for my application, and this tool is the closest I found for comfortable kernel debugging...So i'd like to know of this project is still being maintained.
Thanks for any answers.
edit: I intend to write kernels that will ultimately run on GPUs. Can programs debugged using oclgrind be considered safe for such use?
The text was updated successfully, but these errors were encountered: