Hi,
On 23/11/2023 09:36, Alastair McKinstry wrote:
Hi,
OpenMPI has a new upstream release 5.0.0. It is in experimental now; the
SOVERSION for libraries remains 40.X (minor version increment), there is an
SOVERSION increment for private libraries only so in theory this is not an ABI
transition. However 5.0.0 drops 32-bit system support.
The default MPI implementation for each architecture is set in mpi-defaults;
this allows a per-arch MPI choice; in practice we currently use OpenMPI for all
archs. The other choice is MPICH.
So the question becomes: do we switch MPI for just 32-bit archs, or all? What
are the release teams opinion on this transition?
Having the same implementation across the board makes things easier for testing
purposes et al, however I don't see that as a blocker for not having separate
implementations.
What are your thoughts on it? Is there a strong reason why we should stick with
OpenMPI for 64bit releases? Or from a different POV, what are the risks of
changing the implementation? Introducing a different set of bugs?
For release architectures, the 32bit ones would be armel, armhf and i386.
Cheers,
Emilio
