As the _c API provides exactly the same functionality as the _x when are we deprecating the _X API ?

  George.


On Wed, Jul 7, 2021 at 1:23 PM Dan Holmes via mpi-forum <mpi-forum@lists.mpi-forum.org> wrote:
Hi Ken,

Looks like an oversight to me.

It needs a fix in "chap-ei/ei-2.tex” on line 575 of 668
from "XFER_NUM_ELEM_SMALL”,
to “POLYXFER_NUM_ELEM_NNI",

Cheers,
Dan.
Dr Daniel Holmes PhD
Executive Director
Chief Technology Officer
CHI Ltd



On 7 Jul 2021, at 15:37, Raffenetti, Kenneth J. via mpi-forum <mpi-forum@lists.mpi-forum.org> wrote:

Hi,

This issue was raised in the MPICH GitHub https://github.com/pmodels/mpich/issues/5413.

In MPI-3.1, we have C bindings for:

int MPI_Get_elements(const MPI_Status *status, MPI_Datatype datatype, int *count)
int MPI_Get_elements_x(const MPI_Status *status, MPI_Datatype datatype, MPI_Count *count)
int MPI_Status_set_elements(MPI_Status *status, MPI_Datatype datatype, int count)
int MPI_Status_set_elements_x(MPI_Status *status, MPI_Datatype datatype, MPI_Count count)

MPI-4.0 added:

int MPI_Get_elements_c(const MPI_Status *status, MPI_Datatype datatype, MPI_Count *count)

But no binding was added for an _c version of MPI_Status_set_elements. Was this intended?

Thanks,
Ken

_______________________________________________
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

_______________________________________________
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum