Seems like it is a 32 bit bug, I replicated it on another 32 bit machine and filed a bug report: http://projects.scipy.org/numpy/ticket/2017
As for a temporary fix, I also register uintp32 (and intp32 for good luck) to DTYPES_TO_CTYPES which seems to do the trick (on 64 bit it will just overwrite the key but link it to the same value). On Thu, Jan 12, 2012 at 7:08 PM, Josh Bleecher Snyder <[email protected]> wrote: >> Can anyone test if this replicates with his numpy (mine is 1.6.1)? > > For what it's worth: > > > Ubuntu, 64bit, Python 2.6.5: > >>>> np.version.version > '1.3.0' >>>> np.dtype(np.uintp) > dtype('uint64') >>>> np.dtype(np.uintp) == np.dtype(np.uint64) > True >>>> hash(np.dtype(np.uintp)) > 1667532113121643636 >>>> hash(np.dtype(np.uint64)) > 1667532113121643636 > > > Ubuntu, 64bit, Python 2.6.5: > >>>> np.version.version > '1.6.0' >>>> np.dtype(np.uintp) > dtype('uint64') >>>> np.dtype(np.uintp) == np.dtype(np.uint64) > True >>>> hash(np.dtype(np.uintp)) > -7981643793158015352 >>>> hash(np.dtype(np.uint64)) > -7981643793158015352 > > > OS X, 64bit, Python 2.6.5: > >>>> np.version.version > '1.6.0' >>>> np.dtype(np.uintp) > dtype('uint64') >>>> np.dtype(np.uintp) == np.dtype(np.uint64) > True >>>> hash(np.dtype(np.uintp)) > -7981643793158015352 >>>> hash(np.dtype(np.uint64)) > -7981643793158015352 > > So...haven't been able to reproduce it here. > > -josh _______________________________________________ PyCUDA mailing list [email protected] http://lists.tiker.net/listinfo/pycuda
