Upgrade macos

This commit is contained in:
Bassem Girgis
2025-03-19 08:52:56 -05:00
parent 53580cb51f
commit d29ef955f5
8041 changed files with 1936720 additions and 130842 deletions

View File

@@ -1,57 +1,48 @@
.TH MPI_Intercomm_create 3 "6/5/2019" " " "MPI"
.TH MPI_Intercomm_create 3 "2/3/2025" " " "MPI"
.SH NAME
MPI_Intercomm_create \- Creates an intercommuncator from two intracommunicators
.SH SYNOPSIS
.nf
int MPI_Intercomm_create(MPI_Comm local_comm, int local_leader,
MPI_Comm peer_comm, int remote_leader, int tag, MPI_Comm * newintercomm)
.fi
.nf
int MPI_Intercomm_create(MPI_Comm local_comm, int local_leader,
MPI_Comm peer_comm, int remote_leader, int tag,
MPI_Comm *newintercomm)
.fi
.SH INPUT PARAMETERS
.PD 0
.TP
.B local_comm
- Local (intra)communicator
- local intra-communicator (handle)
.PD 1
.PD 0
.TP
.B local_leader
- Rank in local_comm of leader (often 0)
- rank of local group leader in local_comm (integer)
.PD 1
.PD 0
.TP
.B peer_comm
- Communicator used to communicate between a
designated process in the other communicator.
Significant only at the process in
.I local_comm
with
rank
.I local_leader
\&.
- `peer communicator; significant only at the local_leader (handle)
.PD 1
.PD 0
.TP
.B remote_leader
- Rank in peer_comm of remote leader (often 0)
- rank of remote group leader in peer_comm; significant only at the local_leader (integer)
.PD 1
.PD 0
.TP
.B tag
- Message tag to use in constructing intercommunicator; if multiple
.I MPI_Intercomm_creates
are being made, they should use different tags (more
precisely, ensure that the local and remote leaders are using different
tags for each
.I MPI_intercomm_create
).
- tag (integer)
.PD 1
.SH OUTPUT PARAMETERS
.PD 0
.TP
.B newintercomm
- Created intercommunicator
- new inter-communicator (handle)
.PD 1
.SH NOTES
@@ -64,7 +55,7 @@ in the
The MPI 1.1 Standard contains two mutually exclusive comments on the
input intercommunicators. One says that their repective groups must be
input intercommunicators. One says that their respective groups must be
disjoint; the other that the leaders can be the same process. After
some discussion by the MPI Forum, it has been decided that the groups must
be disjoint. Note that the
@@ -136,7 +127,7 @@ its use is deprecated. The predefined error handler
may be used to cause error values to be returned.
Note that MPI does
.B not
guarentee that an MPI program can continue past
guarantee that an MPI program can continue past
an error; however, MPI implementations will attempt to continue whenever
possible.
@@ -147,6 +138,14 @@ possible.
.PD 1
.PD 0
.TP
.B MPI_ERR_ARG
- Invalid argument. Some argument is invalid and is not
identified by a specific error class (e.g.,
.I MPI_ERR_RANK
).
.PD 1
.PD 0
.TP
.B MPI_ERR_COMM
- Invalid communicator. A common error is to use a null
communicator in a call (not even allowed in
@@ -175,29 +174,13 @@ the attribute
.PD 1
.PD 0
.TP
.B MPI_ERR_INTERN
- This error is returned when some part of the MPICH
implementation is unable to acquire memory.
.PD 1
.PD 0
.TP
.B MPI_ERR_RANK
- Invalid source or destination rank. Ranks must be between
zero and the size of the communicator minus one; ranks in a receive
(
.I MPI_Recv
,
.I MPI_Irecv
,
.I MPI_Sendrecv
, etc.) may also be
.I MPI_ANY_SOURCE
\&.
.B MPI_ERR_OTHER
- Other error; use
.I MPI_Error_string
to get more information
about this error code.
.PD 1
.SH SEE ALSO
MPI_Intercomm_merge, MPI_Comm_free, MPI_Comm_remote_group,
MPI_Intercomm_merge, MPI_Comm_free, MPI_Comm_remote_group, MPI_Comm_remote_size
.br
MPI_Comm_remote_size