forked from open-mpi/ompi
-
Notifications
You must be signed in to change notification settings - Fork 1
6.0.x FeatureList
Jeff Squyres edited this page Oct 20, 2018
·
4 revisions
No timeline estimated yet. Probably not until summer 2020 at the earliest.
-
Remove TKR version of
use mpimodule.- This was deferred from 4.0.x because in April/May 2018 (and then deferred again from v5.0.x in October 2018), it was discovered that:
- The RHEL 7.x default gcc (4.8.5) still uses the TKR
mpimodule - The NAG compiler still uses the TKR
mpimodule.
- The RHEL 7.x default gcc (4.8.5) still uses the TKR
- Is it time to re-evaluate? (RHEL 7 is going to be around for a while -- it may take a while before we can delete the the TKR
mpimodule, but keeping this item here for completeness) - 😢
- This was deferred from 4.0.x because in April/May 2018 (and then deferred again from v5.0.x in October 2018), it was discovered that:
-
Remove all deleted MPI-1 and MPI-2 functionality
- We removed the C++ bindings in OMPI v5.0 (this bullet being written in Oct 2018, long before v5.0.0 was even forked, so make sure that that actually happened).
- Is it time to remove
MPI_ATTR_DELETE, etc.?- These were all been marked as "deprecated" (possibly in 2.0.x series? definitely by the 3.0.x series).
- In the v4.0.x series, the C++ bindings are not built by default
- In the v4.0.x series, mpi.h/mpif.h/mpi+mpi_f08 modules do not have prototypes/declarations for all the MPI-1 deleted functions and globals (although they still contained the symbols in the libraries for ABI compatibility reasons).
--enable-mpi-compatibilitycould be used to re-add these symbols tompi.h, but emitted deprecated warnings if you used them. - We talked about removing the symbols in v5.0.x -- and almost did it -- but then decided that not enough of the MPI community was going to update from these MPI-1 and MPI-2 functions by v5.0.x (estimate summer 2018).
- We need to re-evaluate for v6.0.0 whether it's ok to remove all these MPI-1/MPI-2 deleted symbols for good (i.e., is the MPI community ready for this).
-
THIS WILL CHANGE ABI, and therefore the major
.soversion oflibmpiwill change. THIS AFFECTS OUR PACKAGERS. We talked about this with our packagers in the v4.0.x timeframe, but we should remind them of this change (see https://github.com/open-mpi/ompi/issues/5447 and https://www.mail-archive.com/[email protected]/msg00015.html for a bit more history on what happened in the v4.0.x timeframe).