v4.0.x: ompi_info field for MPI-1 compat symbols in mpi.h? #6470
Assignees
Labels
Comments
|
Good idea. I'll give this a go today. |
hppritcha
added a commit
to hppritcha/ompi
that referenced
this issue
Mar 7, 2019
Its so easy to misspell compatability (sic) that we need to have ompi_info help us out. Related to open-mpi#6470 Signed-off-by: Howard Pritchard <[email protected]>
hppritcha
added a commit
to hppritcha/ompi
that referenced
this issue
Mar 7, 2019
Its so easy to misspell compatability (sic) that we need to have ompi_info help us out. Related to open-mpi#6470 Signed-off-by: Howard Pritchard <[email protected]>
hppritcha
added a commit
to hppritcha/ompi
that referenced
this issue
Mar 11, 2019
Its so easy to misspell compatability (sic) that we need to have ompi_info help us out. Related to open-mpi#6470 Signed-off-by: Howard Pritchard <[email protected]> (cherry picked from commit a5ba48c)
hppritcha
added a commit
to hppritcha/ompi
that referenced
this issue
Mar 11, 2019
MPI1 compat disabled beyond v4.0.x Related to open-mpi#6470 Signed-off-by: Howard Pritchard <[email protected]>
|
closing as both master and v4.0.x have been updated |
markalle
pushed a commit
to markalle/ompi
that referenced
this issue
Sep 12, 2020
Its so easy to misspell compatability (sic) that we need to have ompi_info help us out. Related to open-mpi#6470 Signed-off-by: Howard Pritchard <[email protected]> (cherry picked from commit a5ba48c)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While reading #6469, I realized that there's no
ompi_infofield indicating whethermpi.hincludes the MPI-1 compat symbols or not.We should probably add this. Should be a trivial thing to add.
It might be specific just to v4.0.x, but maybe we might want to add it to master (just hard-coded to "no") for continuity into v5.0.x...?
The text was updated successfully, but these errors were encountered: