On 26 August 2014 21:29, George Bosilca <bosi...@icl.utk.edu> 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. Please note that the "callbacks" I'm talking about are the ones registered for freeing cached attributes, their invocation is tied to the lifetime of the MPI handle. The callbacks you are talking about are different kind of beasts, they are callbacks you what to run specifically at MPI_Finalize(). Caching duplicated communicators is a key feature in many libraries. How do you propose to handle the deallocation of the duped communicators when COMM_WORLD is involved? -- Lisandro Dalcin ============ Research Scientist Computer, Electrical and Mathematical Sciences & Engineering (CEMSE) Numerical Porous Media Center (NumPor) King Abdullah University of Science and Technology (KAUST) http://numpor.kaust.edu.sa/ 4700 King Abdullah University of Science and Technology al-Khawarizmi Bldg (Bldg 1), Office # 4332 Thuwal 23955-6900, Kingdom of Saudi Arabia http://www.kaust.edu.sa Office Phone: +966 12 808-0459
