Currently, MPI does not mandate any MPI_T entities to be implemented which makes it hard for portable tools to work across different MPI implementations. Furthermore, some entities only make sense in the context of other entities as in an "all or nothing" approach.
Proposal
To retain MPI_T's philosophy of not mandating specific entities to be present, a side document should define specific entities or groups of entities with specific semantics. Then if an MPI implementation claims to implement a specific entity that is listed, it will have to follow the specified semantics.
Changes to the Text
tbd.
Impact on Implementations
Implementors can choose whether to implement a specific set of MPI_T entities or not.
Impact on Users
Tool developers could rely on specific semantics when an entity is discovered to be supported.
Problem
Currently, MPI does not mandate any MPI_T entities to be implemented which makes it hard for portable tools to work across different MPI implementations. Furthermore, some entities only make sense in the context of other entities as in an "all or nothing" approach.
Proposal
To retain MPI_T's philosophy of not mandating specific entities to be present, a side document should define specific entities or groups of entities with specific semantics. Then if an MPI implementation claims to implement a specific entity that is listed, it will have to follow the specified semantics.
Changes to the Text
tbd.
Impact on Implementations
Implementors can choose whether to implement a specific set of MPI_T entities or not.
Impact on Users
Tool developers could rely on specific semantics when an entity is discovered to be supported.
References and Pull Requests