All of my testing on 2.0.1rc3 is complete except for SPARC. The alignment issue on SPARC *has* been tested via 2.0.1rc2 + patch (so there is very low probability that 2.0.1rc3 would fail).
At this point I am aware of only two platforms that fail that we didn't already know about: + OpenBSD-6.0 disallows the "patcher" call to mprotect() unless you make the required animal sacrifice (or something close to it!) + Geoffroy's reported problems w/ atomics on PPC64 with PGI-16.x (yes, PGI for PPC), which is issue open-mpi/ompi#2044 <https://github.com/open-mpi/ompi/issues/2044> I mention these only for completeness, and don't advocate holding up a 2.0.1 release for either. -Paul On Thu, Sep 1, 2016 at 1:47 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> wrote: > We're getting close. Unless any showstoppers show up in the immediate > future, we will likely be releasing this as 2.0.1: > > rc3 tarballs here: > > https://www.open-mpi.org/software/ompi/v2.0/ > > Changes since rc2: > > - Fix COMM_SPAWN segv > - Fix yalla bandwidth issue > - Fix an OMPIO-related crash when using built-in datatypes > - Fix a Solaris alignment issue > - Fix a stdin problem > - Fix a bunch of typos and make other updates in README > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: http://www.cisco.com/web/ > about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > devel@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/devel > -- Paul H. Hargrove phhargr...@lbl.gov Computer Languages & Systems Software (CLaSS) Group Computer Science Department Tel: +1-510-495-2352 Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
_______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
