It seems that I was looking at a wrong line and referred to the as_buffer
method for the pointer_holder_base class that was fixed.
The same fix is needed for the device_allocation class as well, I believe:
On Thu, Jun 7, 2018 at 4:53 PM, Yiyin Zhou <heerozhou(a)gmail.com> wrote:
I ran into issues when running the following gist written by Lev.
Basically the code works fine under Python 2.7 but I got the following
error in Python 3.6 (both with openmpi 3.0.0 and mpi4py 3.0.0).
Traceback (most recent call last):
File "mpi4py_pycuda_demo.py", line 64, in <module>
comm.Recv([bufint(x_gpu), dtype_to_mpi(x_gpu.dtype)], source=0)
File "mpi4py/MPI/Comm.pyx", line 283, in mpi4py.MPI.Comm.Recv
File "mpi4py/MPI/msgbuffer.pxi", line 402, in mpi4py.MPI.message_p2p_recv
File "mpi4py/MPI/msgbuffer.pxi", line 388, in
File "mpi4py/MPI/msgbuffer.pxi", line 155, in mpi4py.MPI.message_simple
File "mpi4py/MPI/msgbuffer.pxi", line 94, in mpi4py.MPI.message_basic
File "mpi4py/MPI/asbuffer.pxi", line 308, in mpi4py.MPI.getbuffer
File "mpi4py/MPI/asbuffer.pxi", line 135, in mpi4py.MPI.PyMPI_GetBuffer
BufferError: memoryview: underlying buffer is not writable
I am using 2017.1.1, so presumably the as_buffer method should already
return a writable buffer from a fix two years ago. Any suggestion is