Hi, > This thread saved me some debugging : > http://www.khronos.org/message_boards/showthread.php/7426-clBuildProgram-return-45-error
excellent catch, good to know! > As weird as it sounds, clBuildProgram can build an incorrect kernel > which will lead to CL_INVALID_PROGRAM_EXECUTABLE when the kernel is > added. The build log, however, will not be empty in this case. I've > experienced this when I used fabs(int) in a kernel. clBuildProgram > return CL_SUCCESS but the binary kernel was garbage. > > How should we handle this in ViennaCL? I would suggest always printing > the build log (but not the source) when VIENNACL_DEBUG_BUILD is set. Agreed, that makes perfect sense for VIENNACL_DEBUG_BUILD. Also, I'd like to suggest to always check clGetProgramBuildInfo(..., CL_PROGRAM_BUILD_STATUS, ...) to be on the safe side. There's nothing worse than a silent data or kernel corruption. Any objections? Best regards, Karli ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
