A while back I had to reinstall windows after an SSD drive failed. I was surprised to find that tried and tested OpenCL code was not working. There are three reasons why: 1) A newer version of the OpenCL driver was released by AMD in that time. It now follows the specification strictly for accessing vector components: This is referred in a thread on intel forums: http://software.intel.com/en-us/forums/showthread.php?t=101684 2) One standard way of getting file size is to use stat. But this seems to cause problem with newline on windows, even after duplicating the text in windows format. 3) Build log was not big enough to display all the above errors, for each wrongly placed index, for each unidentified character. The build log is too big. 4096 is not enough space for errors! There is no query for how large the build log will be. The return value does specify the written amount. One could check to see the limit, resize the buffer, then rebuild. Then again, this is only needed for Debug, so leave it out for Release version. There is nothing wrong with OpenCL C bindings as I had feared! |