Junchao Zhang writes:
> On Fri, Oct 22, 2021 at 9:13 PM Barry Smith wrote:
>
>>
>> One technical reason is that PetscHeaderDestroy_Private() may call
>> PetscCommDestroy() which may call MPI_Comm_free() which is defined by the
>> standard to be collective. Though PETSc tries to limit its use
On Fri, Oct 22, 2021 at 9:13 PM Barry Smith wrote:
>
> One technical reason is that PetscHeaderDestroy_Private() may call
> PetscCommDestroy() which may call MPI_Comm_free() which is defined by the
> standard to be collective. Though PETSc tries to limit its use of new MPI
> communicators (for
One technical reason is that PetscHeaderDestroy_Private() may call
PetscCommDestroy() which may call MPI_Comm_free() which is defined by the
standard to be collective. Though PETSc tries to limit its use of new MPI
communicators (for example generally many objects shared the same
Dear PETSc users,
What is the main reason underlying PetscDestroy subroutines having
global collective semantics? Is this actually true for all PETSc
objects? Can this be relaxed/deactivated by, e.g., compilation
macros/configuration options?
Thanks in advance!
Best regards,
Alberto.
