Hi Anthony, On Thu, 2 Jun 2011 12:28:03 -0400, Anthony LaTorre <[email protected]> wrote: > I noticed in the test source code that kernel functions are called with the > keyword *texrefs* containing a list of texture references; my code seems to > be unaffected whether I include this keyword argument or not. What is the * > texrefs* keyword argument used for?
That's a great question. I just removed all the 'texrefs' arguments from PyCUDA's test code, and everything still works, as you indicate. What the 'texrefs' argument does is call cuParamsetTexRef, whose documentation [1] makes it sound like calling it is necessary. But it appears that that's not really true. For lack of better documentation (anyone know of anything better?), I can't tell what the 'officially correct' way is. [1] http://developer.download.nvidia.com/compute/cuda/2_3/toolkit/docs/online/group__CUEXEC_g1a5321b5fb1d83d6c4f3d51dd976579e.html#g1a5321b5fb1d83d6c4f3d51dd976579e Andreas
pgpImEQ3elwKK.pgp
Description: PGP signature
_______________________________________________ PyCUDA mailing list [email protected] http://lists.tiker.net/listinfo/pycuda
