Because we’ve screwed up in the past? I think the ompi_message_null was me, and I was in a hurry to prototype for the MPI Forum. And then it stuck.
Brian On 2/1/23, 3:16 AM, "users on behalf of Jeff Hammond via users" <users-boun...@lists.open-mpi.org<mailto:users-boun...@lists.open-mpi.org> on behalf of users@lists.open-mpi.org<mailto:users@lists.open-mpi.org>> wrote: Why do the null handles not follow a consistent scheme, at least in Open-MPI 4.1.2? ompi_mpi_<handle>_null is used except when handle={request,message}, which drop the "mpi_". The above have an associated ..null_addr except ompi_mpi_datatype_null and ompi_message_null. Why? Jeff Open MPI v4.1.2, package: Debian OpenMPI, ident: 4.1.2, repo rev: v4.1.2, Nov 24, 2021 $ nm -gD /usr/lib/x86_64-linux-gnu/libmpi.so | grep ompi | grep null | grep -v fn 0000000000134040 B ompi_message_null 0000000000126300 B ompi_mpi_comm_null 0000000000115898 D ompi_mpi_comm_null_addr 0000000000120f40 D ompi_mpi_datatype_null 000000000012cb00 B ompi_mpi_errhandler_null 0000000000116030 D ompi_mpi_errhandler_null_addr 0000000000134660 B ompi_mpi_file_null 00000000001163e8 D ompi_mpi_file_null_addr 0000000000126200 B ompi_mpi_group_null 0000000000115890 D ompi_mpi_group_null_addr 000000000012cf80 B ompi_mpi_info_null 0000000000116038 D ompi_mpi_info_null_addr 0000000000133720 B ompi_mpi_op_null 00000000001163c0 D ompi_mpi_op_null_addr 0000000000135740 B ompi_mpi_win_null 0000000000117c80 D ompi_mpi_win_null_addr 000000000012d080 B ompi_request_null 0000000000116040 D ompi_request_null_addr -- Jeff Hammond jeff.scie...@gmail.com<mailto:jeff.scie...@gmail.com> http://jeffhammond.github.io/
