On 09/23/2011 09:48 AM, Jeff Squyres wrote:
(...)
> However, we ultimately discarded it when someone showed a real-world code
> that used *multiple* wrapper compilers (i.e., one wrapper compiler invoked
> another, which, in turn, invoked another, and then finally invoked the
> real/underlying
On 09/23/2011 06:40 AM, Jeff Squyres wrote:
(...)
> Unless there is an effort undertaken to standardize wrapper compiler flags,
> this is not going to happen. Indeed, as I mentioned in a prior email, some
> MPI implementations do not have wrapper compilers at all. This makes
> standardizatio
On 03/09/2011 09:44 AM, Jeff Squyres wrote:
The MPI_Comm_connect and MPI_Comm_accept calls are collective over their entire
communicators.
So if you pass MPI_COMM_WORLD into MPI_Comm_connect/accept, then *all*
processes in those respective MPI_COMM_WORLD's need to call
MPI_Comm_connect/accept
Hello,
I'm trying to connect two independent MPI process groups with an
intercommunicator, using ports, as described in sec. 10.4 of the MPI
standard. One group runs a server, the other a client. The server
opens a port, publishes the port's name, and waits for a connection.
The client obt
