Is there a formal way to debug CAL or Brook+ kernels, or are we presently relegated to commenting things out can changing what the kernel computes to verify each stage?
Brook+ generates CPU codegen that can be debugged if you set BRT_RUNTIME=cpu env variable. Though the code generated is difficult to debug as it uses various classes to represent data rather than directly using pointers. But, still it wroks as a great debugging tool to find problems with your kernel and also as a reference point for your algorithm correctness.
Awesome. Next time I have a problem, I'll try that.
Retrieving data ...