---
name: "MPI_Allgather_c"
section: "3"
platform: "linux"
package: "mpich-doc"
version: "4.0.2-3"
release: "Debian 12 (Bookworm)"
platforms: ["linux"]
url: "https://new.carta.tech/MPI_Allgather_c"
---

# MPI\_Allgather\_c(3)

Gathers data from all tasks and distribute the combined data to all tasks

## NAME

MPI\_Allgather\_c -  Gathers data from all tasks and distribute the combined data to all tasks

## SYNOPSIS

```
int MPI_Allgather_c(const void *sendbuf, MPI_Count sendcount, MPI_Datatype sendtype, void *recvbuf,
MPI_Count recvcount, MPI_Datatype recvtype, MPI_Comm comm)
```

## INPUT PARAMETERS

- **sendbuf**

  \- starting address of send buffer (choice) (choice)

- **sendcount**

  \- number of elements in send buffer (non-negative integer) (non-negative integer)

- **sendtype**

  \- data type of send buffer elements (handle) (handle)

- **recvcount**

  \- number of elements received from any process (non-negative integer) (non-negative integer)

- **recvtype**

  \- data type of receive buffer elements (handle) (handle)

- **comm**

  \- communicator (handle) (handle)

## OUTPUT PARAMETERS

- **recvbuf**

  \- address of receive buffer (choice) (choice)

## NOTES

The MPI standard (1.0 and 1.1) says that\

The jth block of data sent from  each process is received by every process and placed in the jth block of the buffer  *recvbuf* .

This is misleading; a better description is\

The block of data sent from the jth process is received by every process and placed in the jth block of the buffer  *recvbuf* .

This text was suggested by Rajeev Thakur and has been adopted as a clarification by the MPI Forum.

## THREAD AND INTERRUPT SAFETY

This routine is thread-safe.  This means that this routine may be safely used by multiple threads without the need for any user-provided thread locks.  However, the routine is not interrupt safe.  Typically, this is due to the use of memory allocation routines such as  *malloc* or other non-MPICH runtime routines that are themselves not interrupt-safe.

## NOTES FOR FORTRAN

All MPI routines in Fortran (except for  *MPI\_WTIME* and  *MPI\_WTICK* ) have an additional argument  *ierr* at the end of the argument list.   *ierr* is an integer and has the same meaning as the return value of the routine in C.  In Fortran, MPI routines are subroutines, and are invoked with the *call* statement.

All MPI objects (e.g.,  *MPI\_Datatype* ,  *MPI\_Comm* ) are of type  *INTEGER* in Fortran.

## ERRORS

All MPI routines (except  *MPI\_Wtime* and  *MPI\_Wtick* ) return an error value; C routines as the value of the function and Fortran routines in the last argument.  Before the value is returned, the current MPI error handler is called.  By default, this error handler aborts the MPI job.  The error handler may be changed with  *MPI\_Comm\_set\_errhandler* (for communicators), *MPI\_File\_set\_errhandler* (for files), and  *MPI\_Win\_set\_errhandler* (for RMA windows).  The MPI-1 routine  *MPI\_Errhandler\_set* may be used but its use is deprecated.  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; however, MPI implementations will attempt to continue whenever possible.

- **MPI\_SUCCESS**

  \- No error; MPI routine completed successfully.

- **MPI\_ERR\_BUFFER**

  \- Invalid buffer pointer.  Usually a null buffer where one is not valid.

- **MPI\_ERR\_COMM**

  \- Invalid communicator.  A common error is to use a null communicator in a call (not even allowed in  *MPI\_Comm\_rank* ).

- **MPI\_ERR\_COUNT**

  \- Invalid count argument.  Count arguments must be  non-negative; a count of zero is often valid.

- **MPI\_ERR\_TYPE**

  \- Invalid datatype argument.  Additionally, this error can occur if an uncommitted MPI\_Datatype (see  *MPI\_Type\_commit* ) is used in a communication call.

- **MPI\_ERR\_OTHER**

  \- Other error; use  *MPI\_Error\_string* to get more information about this error code.