Lisandro,
We all use similar mechanisms to handle internal releases. Let's give some
credit to the MPI folks who (for once) designed a clear and workable
mechanism to achieve this.
George.
On Wed, Aug 27, 2014 at 10:15 AM, Lisandro Dalcin wrote:
> On 26 August 2014 23:59, George Bosilca w
On 26 August 2014 23:59, George Bosilca wrote:
> Lisandro,
>
> You rely on a feature clearly prohibited by the MPI standard. Please read
> the entire section I pinpointed you to (8.7.1).
>
> There are 2 key sentences in the section.
>
> 1. When MPI_FINALIZE is called, it will first execute the equ
Lisandro,
You rely on a feature clearly prohibited by the MPI standard. Please read
the entire section I pinpointed you to (8.7.1).
There are 2 key sentences in the section.
1. When MPI_FINALIZE is called, it will first execute the equivalent of an
MPI_COMM_FREE on MPI_COMM_SELF.
2. The freeing
On 26 August 2014 21:29, George Bosilca wrote:
> The MPI standard clearly states (in 8.7.1 Allowing User Functions at Process
> Termination) that the mechanism you describe is only allowed on
> MPI_COMM_SELF. The most relevant part starts at line 14.
>
IMHO, you are misinterpreting the standard.
The MPI standard clearly states (in 8.7.1 Allowing User Functions at
Process Termination) that the mechanism you describe is only allowed on
MPI_COMM_SELF. The most relevant part starts at line 14.
George.
On Tue, Aug 26, 2014 at 11:20 AM, Lisandro Dalcin wrote:
> Another issue while testing
Another issue while testing 1.8.2 (./configure --enable-debug
--enable-mem-debug).
Please look at the following code. I'm duplicating COMM_WORLD and
composing the dupe on it. The attribute free function is written to
Comm_free the duped comm and deallocate memory. However, the run fails
with the e
