You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For historical reasons MPI uses int, MPI_Aint, MPI_Offset, and MPI_Count, which may have different ranges and signedness. Integer usage should be harmonized for MPL:
size_t and ssize_t (when negative values are permissible) should be the only integer types.
It must be checked for narrowing when passing integer values to underlying MPI library functions.
@VictorEijkhout I am not following the discussion in detail. Thanks, for drawing my attention to these newer developments. Apparently, there are "a few" new MPI functions on the way.
For historical reasons MPI uses
int
,MPI_Aint
,MPI_Offset
, andMPI_Count
, which may have different ranges and signedness. Integer usage should be harmonized for MPL:size_t
andssize_t
(when negative values are permissible) should be the only integer types.Edit: MPI 4.0 will introduce large-count support via new functions, see https://eurompi.github.io/assets/papers/2020-09-eurompi2020-mpi4.pdf
The text was updated successfully, but these errors were encountered: