[Mpi-forum] ABI working group is live

[Guillaume Mercier]

Hello Jeff,

Could you add me to the group?
My github id is GuillaumeMercier

My email address is guillaume.mercier at u-bordeaux.fr

Thanks
Guillaume


On 09/12/2022 07:31, Jeff Hammond via mpi-forum wrote:
> The MPI ABI workgroup was approved.  You can sign up for the mailing 
> list now: https://lists.mpi-forum.org/mailman/listinfo/mpiwg-abi 
> <https://lists.mpi-forum.org/mailman/listinfo/mpiwg-abi>.
> 
> If you want access to the GitHub group (https://github.com/mpiwg-abi/ 
> <https://github.com/mpiwg-abi/>), send me your GitHub username.
> 
> If you want access to the Slack channel, DM me on Slack.  If you are not 
> on Slack already, send me your email address.
> 
> Jeff
> 
> On Wed, Nov 16, 2022 at 9:54 AM Jeff Hammond <jeff.science at gmail.com 
> <mailto:jeff.science at gmail.com>> wrote:
> 
>     I don't know what we do to create new working groups with the
>     post-COVID rules, but I would like to create and chair a WG focused
>     on ABI standardization.
> 
>     There is strong support for this effort in many user communities,
>     including developers and maintainers of Spack, mpi4py, Julia MPI
>     (MPI.jl), Rust MPI (rsmpi), PETSc and NVHPC SDK, to name a few. 
>     There are even a few implementers who have expressed support, but I
>     won't name them for their own protection.
> 
>     The problem is so exasperating for our users that there are at least
>     two different projects devoted to mitigating ABI problems (not
>     including shims built in to the aforementioned MPI wrappers):
> 
>     https://github.com/cea-hpc/wi4mpi <https://github.com/cea-hpc/wi4mpi>
>     https://github.com/eschnett/MPItrampoline
>     <https://github.com/eschnett/MPItrampoline>
> 
>     I've written about this a bit already, for those who are
>     interested.  More material will be forthcoming once I have time for
>     more experiments.
> 
>     https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI.md
>     <https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI.md>
>     https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_2.md <https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_2.md>
>     https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_3.md <https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_3.md>
>     https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_4.md <https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_4.md>
> 
>     I understand this is a controversial topic, particularly for
>     implementers.  I hope that we can proceed objectively.
> 
>     Thanks,
> 
>     Jeff
> 
>     -- 
>     Jeff Hammond
>     jeff.science at gmail.com <mailto:jeff.science at gmail.com>
>     http://jeffhammond.github.io/ <http://jeffhammond.github.io/>
> 
> 
> 
> -- 
> Jeff Hammond
> jeff.science at gmail.com <mailto:jeff.science at gmail.com>
> http://jeffhammond.github.io/ <http://jeffhammond.github.io/>
> 
> _______________________________________________
> mpi-forum mailing list
> mpi-forum at lists.mpi-forum.org
> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0xF63A997035501534.asc
Type: application/pgp-keys
Size: 10971 bytes
Desc: OpenPGP public key
URL: <http://lists.mpi-forum.org/pipermail/mpi-forum/attachments/20230104/449c2e6a/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.mpi-forum.org/pipermail/mpi-forum/attachments/20230104/449c2e6a/attachment.sig>