Hi Peter, this has been fixed (or rather, worked around at) a little bit more cleanly in the version in the git repo to which you might want to upgrade to.
Thomas On Wed, Feb 1, 2012 at 12:28 PM, Peter Rösch <[email protected]> wrote: >> >> I'm as confused as you. Can you go up the call stack and see who made >> that dtype, and how? >> >> Andreas >> >> > after updating to pycuda-2011.2.2 and pyopencl-2011.2 the message described > by Thomas turned up on my Debian squeeze boxes (32 and 64 bit): > cuda 4.1 > python 2.6.6 > numpy 1.4.1 > > Finally, the pycuda and pyopencl examples run on my systems after modifying > the files > pycuda-2011.2.2/pycuda/compyte/dtypes.py > and > pyopencl-2011.2/pyopencl/compyte/dtypes.py > such that strings are used as keys in the dictionaries. > > In _fill_dtype_registry I replaced > > register_dtype(np.bool, "bool") > register_dtype(np.uint8, "unsigned char") > # ... and so on > register_dtype(np.float64, "double") > > with > > register_dtype("bool", "bool") > register_dtype("uint8", "unsigned char") > # ... and so on > register_dtype("float64", "double") > > > and in dtype_to_ctype I replaced > > return DTYPE_TO_NAME[dtype] > > with > > return DTYPE_TO_NAME[str(dtype)] > > Peter > > > _______________________________________________ > PyCUDA mailing list > [email protected] > http://lists.tiker.net/listinfo/pycuda _______________________________________________ PyCUDA mailing list [email protected] http://lists.tiker.net/listinfo/pycuda
