[petsc-dev] Bad use of defined(MPI_XXX)

Jed Brown jed at jedbrown.org
Fri May 24 15:53:40 CDT 2019


"Zhang, Junchao" <jczhang at mcs.anl.gov> writes:

> How about stuff in MPI-2.2 (approved in 2009), the last of MPI-2.x, e.g., PETSC_HAVE_MPI_REDUCE_LOCAL?

Currently we only require MPI-2.0, but I would not object to increasing
to MPI-2.1 or 2.2 if such systems are sufficiently rare (almost
nonexistent) in the wild.  I'm not sure how great the benefits are.

> On Fri, May 24, 2019 at 2:51 PM Jed Brown via petsc-dev <petsc-dev at mcs.anl.gov<mailto:petsc-dev at mcs.anl.gov>> wrote:
> Lisandro Dalcin via petsc-dev <petsc-dev at mcs.anl.gov<mailto:petsc-dev at mcs.anl.gov>> writes:
>
>> These two are definitely wrong, we need PETSC_HAVE_MPI_XXX instead.
>
> Thanks, we can delete both of these cpp guards.
>
>> include/petscsf.h:#if defined(MPI_REPLACE)
>
> MPI-2.0
>
>> src/sys/objects/init.c:#if defined(PETSC_USE_64BIT_INDICES) ||
>> !defined(MPI_2INT)
>
> MPI-1.0


More information about the petsc-dev mailing list