Hey!
This thread saved me some debugging :
http://www.khronos.org/message_boards/showthread.php/7426-clBuildProgram-return-45-error
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.
Philippe
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
ViennaCL-devel mailing list
ViennaCL-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viennacl-devel
