Hmmmwell, we appear to have a problem. According to our Forum reps, those
functions were deprecated by the Forum and hence the standard was actually NOT
updated with "const" declarations. For some odd reason, MPICH went ahead and
updated them anyway - leaving MPICH out of compliance with the
On 03/11/2014 11:30 AM, Jeff Squyres (jsquyres) wrote:
The safest thing for scoreP (and *any* MPI application/middleware) is to not
wholly rely on the MPI_VERSION macros.
From a theoretical sense, the MPI_VERSION macro should be sufficient.
But in reality, the upgrade of an MPI implementatio
The safest thing for scoreP (and *any* MPI application/middleware) is to not
wholly rely on the MPI_VERSION macros.
>From a theoretical sense, the MPI_VERSION macro should be sufficient.
But in reality, the upgrade of an MPI implementation to support all of MPI-3 is
a gradual thing and takes
Can't do much about 1.7.4, but fwiw 1.7.5 will not have this problem - nor will
it be present in 1.8.0 - as we have fully converted to MPI-3 now (and the
version will reflect it).
On Mar 11, 2014, at 10:14 AM, Orion Poplawski wrote:
> FYI -
>
> Looks like the mix of MPI 3 compliant and olde
FYI -
Looks like the mix of MPI 3 compliant and older declarations is causing a
bit of an issue for Score-P support. The current Score-P code bases adding
the const qualifiers on MPI_VERSION >= 3. But openmpi 1.7.4 is still
MPI_VERSION 2 (SUB 2). If I change scorep to add the const qualif
