enh: no memory leaks for blacs_exit and allow re-call #37
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should enable ScaLAPACK/BLACS to be exited and restarted
at will without memory leaks or problems.
When called with blacs_exit(true), the comm_world will be
retained and MPI_Finalized won't be called.
Only when blacs_exit(false) is called will the BI_COMM_WORLD
be de-allocated. So one should expect a memory leak of
an integer if the hosting application calls MPI_Finalize.
For instance the
blacs_exittest example can now be extended to this: