I have an ordinary code, it's builded on top of my lib, which works fine in some samples, so the reasons I can see is function parameters (or their names) mismatch. But it looks fine. But maybe you can say something other ?
I've found that this happens if you don't assign all the parameters to resources. Also, if you're getting the name of a function that doesn't exist as your entry, the kernel is likely to fail (though, if it's "main" this in unlikely to be your problem). Unfortunately, there are many more things that will cause your kernel to execute but your results to be gibberish (like assigning a 1d resource but declaring it as 2d in your kernel).
The result of CalGetErrorString wos <Symbol ">.
1. Try checking CALresult for all CAL APIs. Specially for calCtxGetMem & calCtxSetMem.
2. Have you bind all the symbol handles in shader with a memory handle?
3. Is you memory handle busy? e.g. have you called calResUnmap after calResMap?
Originally posted by: kos The result of CalGetErrorString wos <Symbol ">
The result of CalGetErrorString wos <Symbol ">
In case you wonder, a bug causes calGetErrorString to return a truncated string, see my bug report:
You can work around it by ignoring the NUL char and printing the rest of the string.
Retrieving data ...