SF: treat PETSc builtin datatypes the same way as MPI builtin datatypes

So that we won't duplicate PETSc builtin datatypes like MPIU_2INT. Otherwise,
we can not simply use "if (type != MPIU_2INT) SE

SF: treat PETSc builtin datatypes the same way as MPI builtin datatypes

So that we won't duplicate PETSc builtin datatypes like MPIU_2INT. Otherwise,
we can not simply use "if (type != MPIU_2INT) SETERRQ()" in code.

Add support to unwrap a type created by MPI_Type_contiguous(1,..)
Let dumb types use their own type

show more ...

Added SF GPU support

Move related routines together

Update pack/unpack routines to do packing/unpacking for all neighbors in at most two routines

One is used to pack data in self to self communication; The second is used for remote communication.
So

Update pack/unpack routines to do packing/unpacking for all neighbors in at most two routines

One is used to pack data in self to self communication; The second is used for remote communication.
So that on GPU, we can use at most two kernels to do packing/packing for all neighbors instead of multiple kernels

show more ...

SF: Stricter check for valid inputs in PetscSFCompose

An SF might not encode a true star forest (leaves could be repeated).
Composition of SFs does, however, rely on unique leaves, so check that in

SF: Stricter check for valid inputs in PetscSFCompose

An SF might not encode a true star forest (leaves could be repeated).
Composition of SFs does, however, rely on unique leaves, so check that in
debug mode.

show more ...

SF: Check validity of graph in debug mode

Forbid negative leaf indices in ilocal, negative root indices in
iremote, and invalid ranks in iremote. Since sometimes an SF is used
just to carry informat

SF: Check validity of graph in debug mode

Forbid negative leaf indices in ilocal, negative root indices in
iremote, and invalid ranks in iremote. Since sometimes an SF is used
just to carry information (e.g. DMLocatePoints), do the check when
we're setting up rather than when setting the graph.

show more ...

SF: Handle non-identity local spaces in PetscSFCompose

It is not always the case that the local spaces of the SFs we are
composing are the identity. Remove that implicit assumption, both for
the cas

SF: Handle non-identity local spaces in PetscSFCompose

It is not always the case that the local spaces of the SFs we are
composing are the identity. Remove that implicit assumption, both for
the cases where sfA has a permutation in the local space, and in sfB
where the local space may further be sparse.

show more ...

Add PetscSFComposeInverse and revise PetscSFCompose

Add PetscSF_Neighbor to use MPI3 neighborhood collectives

Add patterned SF graphs and use x as roots and y as leaves in x to y vecscatter

Add op GetGraph in SF so that we can customize it

Add op CreateLocalSF in SF so that we can customize it

Also, we now create local SF on demand (i.e., lazily) since it is not always used.

Optimize the creation of embedded SFs for SFBasic

Implement PetscSFBcast with PetscSFBcastAndOp

Deprecate PetscSFGetRanks with new PetscSFGetRootRanks

Since we have PetscSFGetLeafRanks, it is better to have a similar name.

Add PetscArraycmp(), PetscArraycpy(), PetscArrayzero(), PetscArraymove(), update code to use new forms

Replace a couple multi-mallocs with a single malloc
Replace backwards loops in MatSetValues_*()

Add PetscArraycmp(), PetscArraycpy(), PetscArrayzero(), PetscArraymove(), update code to use new forms

Replace a couple multi-mallocs with a single malloc
Replace backwards loops in MatSetValues_*() with PetscArraymove()

Commit-type: style-fix, feature

show more ...

Update the use of Collective on in the manual pages to reflect the new style

Commit-type: style-fix, documentation
Thanks-to: Patrick Sanan <patrick.sanan@gmail.com>

Man pages: remove .keywords: fields

This field is recognized by doctext from Sowing (http://wgropp.cs.illinois.edu/projects/software/sowing/doctext/node20.htm#Node20),
but it doesn't seem to be unif

Man pages: remove .keywords: fields

This field is recognized by doctext from Sowing (http://wgropp.cs.illinois.edu/projects/software/sowing/doctext/node20.htm#Node20),
but it doesn't seem to be uniformly used or maintained.

Thus, remove all .keywords: fields, and a following blank line, if present.

This is accomplished with GNU sed (gsed on OS X), with the following commands.
*Warning* that this type of command can corrupt a .git directory,
so be cautious in reusing or modifying these commands. They first look
for and delete matching lines with a following line consisting of only whitespace,
and then delete any remaining matching lines.

find src/ -type f -exec gsed -i '/keywords:/ {N; /\n\s*$/d}' {} +
find src/ -type f -exec gsed -i '/keywords:/d' {} +
find include/ -type f -exec gsed -i '/keywords:/ {N; /\n\s*$/d}' {} +
find include/ -type f -exec gsed -i '/keywords:/d' {} +

Hints on the sed command obtained from: https://unix.stackexchange.com/questions/100754/how-to-delete-a-specific-line-and-the-following-blank-line-using-gnu-sed

show more ...

Merge remote-tracking branch 'origin/maint'