On Fri, 11 Mar 2016, Manav Bhatia wrote:
> While we are at it, I have one more observation:
>
> Consider the global comm with ranks {0, 1, 2, 3}.
>
> Then, after the following intended split: {0}, which requires rank
> {0} to request split with a color and ranks {1, 2, 3} with
> MPI_UNDEFINED, th
Looks good to me, Roy.
While we are at it, I have one more observation:
Consider the global comm with ranks {0, 1, 2, 3}.
Then, after the following intended split: {0}, which requires rank {0} to
request split with a color and ranks {1, 2, 3} with MPI_UNDEFINED, the
mpi_communicator on the
On Fri, 11 Mar 2016, Roy Stogner wrote:
> On Fri, 11 Mar 2016, Manav Bhatia wrote:
>
>> From the current status of the code in parallel.h, it looks like
>> mpi_comm_free is called only when _I_duped_it is true, which is
>> true only when Communicator::duplicate() is called.
>>
>> I think the
On Fri, 11 Mar 2016, Manav Bhatia wrote:
> From the current status of the code in parallel.h, it looks like
> mpi_comm_free is called only when _I_duped_it is true, which is
> true only when Communicator::duplicate() is called.
>
> I think the communicator created using split() also needs to
Hi,
From the current status of the code in parallel.h, it looks like
mpi_comm_free is called only when _I_duped_it is true, which is true only when
Communicator::duplicate() is called.
I think the communicator created using split() also needs to be destroyed
using comm_free. But since _I
