George, "Vizkelethy, Gyorgy" <[email protected]> writes: > It was the benchmark.py script, dump-performance.py works fine. When > you are saying that exactly one item workgroup, you mean the CPU test > should have failed for anything but workers = 1? Here is what I get > for the CPU: > > Device compute units: 24 > Device max work group size: 1024 > Device max work item sizes: [1024L, 1L, 1L] > > For the Radeon GPUs I get: > Device compute units: 24 > Device max work group size: 256 > Device max work item sizes: [256L, 256L, 256L]
I haven't looked at benchmark.py in ages. But I'd be happy to take a patch to make it more portable. > One more thing. There are couple of problems with some of the examples. > narray fails on the CPU with clbuildprogram failed: BUILD_PROGRAM_FAILURE - > > Sounds like a driver bug. Is there something about "CVMS server" in the > build log? > Yes, there is. Here is the rest of the error message: > Build on <pyopencl.Device 'Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz' on > 'Apple' at 0xffffffff>: > > CVMS_ERROR_COMPILER_FAILURE: CVMS compiler has crashed or hung building an > element. > (options: -I > /Users/gvizkel/Library/Enthought/Canopy_64bit/User/lib/python2.7/site-packages/pyopencl-2015.2.4-py2.7-macosx-10.6-x86_64.egg/pyopencl/cl) > (source saved as > /var/folders/s1/y1wx_5cj49qdyk7043f80spw000blv/T/tmpormiK4.cl) Yeah, like I thought. Not much we can do short of trying to work around the compiler bugs. > I just did a pip install pyopencl. How do I build it with GL interoperability? Download and unpack the source. ./configure.py --cl-enable-gl python setup.py install Andreas _______________________________________________ PyOpenCL mailing list [email protected] https://lists.tiker.net/listinfo/pyopencl
