Hello Jeff,

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

My email address is guillaume.merc...@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.scie...@gmail.com <mailto:jeff.scie...@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.scie...@gmail.com <mailto:jeff.scie...@gmail.com>
    http://jeffhammond.github.io/ <http://jeffhammond.github.io/>



--
Jeff Hammond
jeff.scie...@gmail.com <mailto:jeff.scie...@gmail.com>
http://jeffhammond.github.io/ <http://jeffhammond.github.io/>

_______________________________________________
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

Attachment: OpenPGP_0xF63A997035501534.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

_______________________________________________
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

Reply via email to