Hi Erik, Erik Schnetter <[email protected]> writes: > On Mon, Aug 20, 2012 at 8:15 PM, Erik Schnetter > <[email protected]> wrote: >> On Mon, Aug 20, 2012 at 7:35 PM, Andreas Kloeckner >> <[email protected]> wrote: >>> Hi there, >>> >>> I'm Andreas Kloeckner, maintainer of PyOpenCL. I reported this bug last >>> night: >>> >>> https://bugs.launchpad.net/pocl/+bug/1038863 >>> >>> I'd love to help you test pocl. In order for this to be easy (and >>> therefore doable within my time constraints), it'd be very useful if >>> that above bug could be fixed, which would allow testing pocl without >>> having to rebuild PyOpenCL. >>> >>> In addition, to avoid requiring ugly workarounds, clGetMemObjectInfo and >>> clGetKernelInfo would need to be implemented--at least partially. >> >> Andreas >> >> Are there any particular parts of these two functions that do you need >> implemented? > > Actually, both were quite easy to implement, all the information is > already present in internal structures. Of course I don't know whether > these structure entries are kept up-to-date... > > These are now available on the branch > <bzr+ssh://bazaar.launchpad.net/~schnetter/pocl/pocl>, to be reviewed.
Thanks for your quick response! Unfortunately, something must be off still, as CL_MEM_TYPE for what should be a buffer object gives 1071312404, i.e. what looks essentially like a random number. Which is not quite surprising, because clCreateBuffer doesn't set that entry... :) Thanks again! Andreas ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
