On Tue, 3 Jan 2012 19:05:39 -0800, William Sheffler <[email protected]> wrote: > Hi PyOpenCL community. > > First, thank you for a great library. I have with been tinkering with > parallel implementations for some of the foundational calculations we > do in our protein structure prediction and design software (Rosetta & > FoldIt), and have found pyopencl to be a real boon for prototyping. > > I am having trouble with empty build logs in cases where I know > significant errors are present. For example, if I try to build a > kernel with such errors in pyopencl and then: > > print program_get_build_logs(self) > > from __init__.py on line 367 (git rev 0a1ca1e9), I get: > > [(<pyopencl.Device 'ATI Radeon HD 6750M' on 'Apple' at 0x1021b00>, '')] > > with an empty build log. If I build the same kernel with the C api's > clBuildProgram and retrive the build log with > clGetProgramBuildInfo(...,CL_PROGRAM_BUILD_LOG,...), I get a long list > of build errors. Can anyone suggest a way I can get a full build log > from pyopencl in these cases.
Here are a few things you can try:
- Remove your PyOpenCL compiler cache
(/tmp/pyopencl-compiler-cache-* on Unix).
- Use pyopencl._Program instead of pyopencl.Program. That version skips
the compiler cache (and does not do lazy building).
- Enable OpenCL API tracing when building PyOpenCL.
Other than that, PyOpenCL simply calls the same function that you
mention, so there's little reason why PyOpenCL should behave differently
From a C program calling the same functions.
Hope this helps, and please let the list know what you find.
Andreas
pgpeWqPS6U1vc.pgp
Description: PGP signature
_______________________________________________ PyOpenCL mailing list [email protected] http://lists.tiker.net/listinfo/pyopencl
