On 06/14/2016 10:37 AM, Jeff Squyres (jsquyres) wrote:
> Per discussion on the webex today, a new nightly snapshot tarball was just
> created for the v2.x branch with all the latest MPI_Request updates:
>
> https://www.open-mpi.org/nightly/v2.x/
>
> Please be sure to test this; we'd like to
We are now feature complete for v2.0.0 and would appreciate testing by
developers and end users before we finalize the v2.0.0 release. In that
light, v2.0.0rc3 is now available:
https://www.open-mpi.org/software/ompi/v2.x/
Here are the changes since 2.0.0rc2:
- The MPI C++ bindings -- which
With a PPC64/Fedora20/gcc-4.8.3 system configuring for "-m32":
configure --prefix=[...] --enable-debug \
CFLAGS=-m32 --with-wrapper-cflags=-m32 \
CXXFLAGS=-m32 --with-wrapper-cxxflags=-m32 \
FCFLAGS=-m32 --with-wrapper-fcflags=-m32 --disable-mpi-fortran
Build fails with
/b
On a little-endian Power8 with XLC-13.1.2 I see a crash not seen with
gcc-4.9.2:
make[4]: Entering directory
'/home/phargrov/OMPI/openmpi-2.0.0rc3-linux-ppc64el-xlc/BLD/ompi/debuggers'
PASS: predefined_gap_test
PASS: predefined_pad_test
/home/phargrov/OMPI/openmpi-2.0.0rc3-linux-ppc64el-xlc/openmp
I am seeing the following errors when using NAG Fortran (v5 or v6):
Error:
/sandbox/hargrove/OMPI/openmpi-2.0.0rc3-linux-x86_64-nagfor-5/openmpi-2.0.0rc3/ompi/mpi/fortran/use-mpi-tkr/mpi_comm_spawn_multiple_f90.f90:
Argument 3 to MPI_COMM_SPAWN_MULTIPLE has data type DOUBLE PRECISION in
reference
Also seen now on a big-endian Power7 with XLC-13.1
-Paul
On Wed, Jun 15, 2016 at 6:20 PM, Paul Hargrove wrote:
> On a little-endian Power8 with XLC-13.1.2 I see a crash not seen with
> gcc-4.9.2:
>
> make[4]: Entering directory
> '/home/phargrov/OMPI/openmpi-2.0.0rc3-linux-ppc64el-xlc/BLD/ompi/
I still see the issue I (re)reported against the previous RC in
https://www.open-mpi.org/community/lists/devel/2016/05/18961.php
-Paul
--
Paul H. Hargrove phhargr...@lbl.gov
Computer Languages & Systems Software (CLaSS) Group
Computer Science Department Tel
I still see failures to build ROMIO on OpenBSD-5.9:
/home/phargrov/OMPI/openmpi-2.0.0rc3-openbsd5-i386/openmpi-2.0.0rc3/ompi/mca/io/romio314/romio/adio/common/ad_fsty
pe.c: In function 'ADIO_FileSysType_fncall':
/home/phargrov/OMPI/openmpi-2.0.0rc3-openbsd5-i386/openmpi-2.0.0rc3/ompi/mca/io/romio3
Paul,
NAG related stuff was added in https://github.com/open-mpi/ompi/pull/1295
Milestone was set to v2.0.1 so no PR was even issued (yet) for the v2.x
branch.
If there is a consensus to update the milestone to v2.0.0, i ll be happy
to PR
Cheers,
Gilles
On 6/16/2016 10:32 AM, Paul Ha
The same failure mode reported below is also occurring on a 32-bit ARM
system.
-Paul
On Wed, Jun 15, 2016 at 6:13 PM, Paul Hargrove wrote:
> With a PPC64/Fedora20/gcc-4.8.3 system configuring for "-m32":
>
> configure --prefix=[...] --enable-debug \
> CFLAGS=-m32 --with-wrapper-cflags=-
Paul,
https://github.com/open-mpi/ompi-release/pull/1178 is ready to be
merged, but the milestone was set to v2.0.1
Cheers,
Gilles
On 6/16/2016 10:40 AM, Paul Hargrove wrote:
I still see failures to build ROMIO on OpenBSD-5.9:
/home/phargrov/OMPI/openmpi-2.0.0rc3-openbsd5-i386/openmpi-
Gilles,
I am just reporting all the issues I find in this RC.
It is up to the core Open MPI developers to decide which ones warrant
attention for 2.0.0.
-Paul
On Wed, Jun 15, 2016 at 6:43 PM, Gilles Gouaillardet
wrote:
> Paul,
>
>
> NAG related stuff was added in https://github.com/open-mpi/om
Ok, that was working. Our PPC64 system is back up and I will finally be able to
fix it tomorrow.
-Nathan
> On Jun 15, 2016, at 7:35 PM, Paul Hargrove wrote:
>
> Also seen now on a big-endian Power7 with XLC-13.1
>
> -Paul
>
> On Wed, Jun 15, 2016 at 6:20 PM, Paul Hargrove wrote:
> On a litt
Will track this one down as well tomorrow.
-Nathan
> On Jun 15, 2016, at 7:13 PM, Paul Hargrove wrote:
>
> With a PPC64/Fedora20/gcc-4.8.3 system configuring for "-m32":
>
> configure --prefix=[...] --enable-debug \
> CFLAGS=-m32 --with-wrapper-cflags=-m32 \
> CXXFLAGS=-m32 --w
14 matches
Mail list logo
