Request Comm::Irsend(const void* \fIbuf\fP, int \fIcount\fP, const
Datatype& \fIdatatype\fP, int \fIdest\fP, int \fItag\fP) const
.SHINPUTPARAMETERS
.ftR
.TP1i
buf
Initial address of send buffer (choice).
.TP1i
count
Number of elements in send buffer (integer).
.TP1i
datatype
Datatype of each send buffer element (handle).
.TP1i
dest
Rank of destination (integer).
.TP1i
tag
Message tag (integer).
.TP1i
comm
Communicator (handle).
.SHOUTPUTPARAMETERS
.ftR
.TP1i
request
Communication request (handle).
.ftR
.TP1i
IERROR
Fortran only: Error status (integer).
.SHDESCRIPTION
.ftR
MPI_Irsend starts a ready-mode nonblocking send. Nonblocking calls allocate a communication request object and associate it with the request handle (the argument request). The request can be used later to query the status of the communication or to wait for its completion.
.sp
A nonblocking send call indicates that the system may start copying data out of the send buffer. The sender should not access any part of the send buffer after a nonblocking send operation is called, until the send completes.
.SHERRORS
Almost all MPI routines return an error value; C routines as the value of the function and Fortran routines in the last argument. C++ functions do not return errors. If the default error handler is set to MPI::ERRORS_THROW_EXCEPTIONS, then on error the C++ exception mechanism will be used to throw an MPI:Exception object.
.sp
Before the error value is returned, the current MPI error handler is
called. By default, this error handler aborts the MPI job, except for I/O function errors. The error handler may be changed with MPI_Comm_set_errhandler; the predefined error handler MPI_ERRORS_RETURN may be used to cause error values to be returned. Note that MPI does not guarantee that an MPI program can continue past an error.