Philippe Tillet <phil.til...@gmail.com> writes: > I remember us already having a problem with strlen on the cache with your > NVidia SDK, which disappeared when you rebooted. Didn't we?
Yes, and I suppose in this case the module reload has had the same effect. But I wish there there could be some way to tell whether these things were transient idiosyncracies of the platform or bugs in our code!! T > 2014-11-05 16:25 GMT-05:00 Toby St Clere Smithe <m...@tsmithe.net>: > >> Toby St Clere Smithe <m...@tsmithe.net> >> writes: >> > The segfault happens when calling (in ocl/context.hpp): >> > >> > 443 err = clGetProgramBuildInfo(temp, devices_[0].id(), >> CL_PROGRAM_BUILD_LOG, 0, NULL, &ret_val_size); >> >> Oh, and the segfault happens in nVidia's OpenCL when it calls strlen >> somewhere.. >> >> Oh, wait.. Apparently my nvidia module was still loaded, so I take back >> the beignet comment (the system defaults to nvidia if it's available; >> what I thought was beignet was therefore not..). >> >> And reloading the nvidia module seems to solve this for nvidia, too. >> >> Very strange. >> >> But the matrix_operations problems still remain! >> >> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> ViennaCL-devel mailing list >> ViennaCL-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/viennacl-devel >> > ------------------------------------------------------------------------------ > > _______________________________________________ > ViennaCL-devel mailing list > ViennaCL-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/viennacl-devel > -- Toby St Clere Smithe http://tsmithe.net ------------------------------------------------------------------------------ _______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
