[OMPI devel] Errors with CXX=pgc++ (but CXX=pgCC OK)

With the 1.10.r5c1 tarball on linux/x86-64 and various versions of the PGI compilers I have configured with --prefix=[...] --enable-debug CC=pgcc CXX=pgc++ FC=pgfortran I see the following with version 14.3 of the PGI compilers: /bin/bash ../../../libtool --tag=CXX --mode=link pgc++ -g -ve

Re: [OMPI devel] [2.0.2rc1] runtime error w/ PGI usempif08 on OpenPOWER

Since the message below has still not appeared in the archive after more then 15hrs, I am resending w/o the attachment. -Paul On Thu, Dec 15, 2016 at 10:23 PM, Paul Hargrove wrote: > On a little-endian Power8 I have the free edition of PGI16.10 for > OpenPOWER. > I am configuring the 2.0.2rc1 ta

Re: [OMPI devel] Wtime is 0.0

> On 16 Dec 2016, at 20:42, Jeff Squyres (jsquyres) wrote: > > If you don't build Open MPI and your application with the same compiler > flags, weird things like this are bound to happen. Make sure Open MPI is > built the same way. Yes, I just did the default install with homebrew. I also ju

Re: [OMPI devel] Wtime is 0.0

If you don't build Open MPI and your application with the same compiler flags, weird things like this are bound to happen. Make sure Open MPI is built the same way. Also, note that the formal signature for MPI_Wtime is to return a DOUBLE PRECISION. REAL(KIND=8) is common, but it is not techni

Re: [OMPI devel] Open MPI v2.0.2rc1 is up

HI Paul, Thanks for the checking the rc out. And for noting the grammar mistake. Howard 2016-12-16 1:00 GMT-07:00 Paul Hargrove : > My testing is complete. > > The only problems not already known are related to PGI's recent "Community > Edition" compilers and have been reported in three separ

Re: [OMPI devel] Wtime is 0.0

I found the problem. It is in the build process which passes -fdefault-real-8 (among other flags) to the compiler: mpif90 -fdefault-real-8 foo.F90 ➜ mpirun -n 1 ./a.out 0.0. Cheers, Jan

Re: [OMPI devel] Wtime is 0.0

> On 16 Dec 2016, at 19:16, Jeff Squyres (jsquyres) wrote: > > On Dec 16, 2016, at 12:48 PM, 🐋 Jan Hegewald wrote: >> >> Your example works fine here too. >> I call Wtime from Fortran code. But if I do the same as in your C example >> 1), it seems to work as well. >> I am puzzled as to what i

Re: [OMPI devel] Wtime is 0.0

On Dec 16, 2016, at 12:48 PM, 🐋 Jan Hegewald wrote: > > Your example works fine here too. > I call Wtime from Fortran code. But if I do the same as in your C example 1), > it seems to work as well. > I am puzzled as to what is causing this. On several HPC clusters everything > is fine. Only on

Re: [OMPI devel] Wtime is 0.0

> On 16 Dec 2016, at 18:02, Jeff Squyres (jsquyres) wrote: > > That's odd; that doesn't happen to me. > > E.g., with this program running on MacOS 10.12.1 with Open MPI 2.0.1, I see a > different value for MPI_Wtime() between successive calls: > > - > $ cat foo.c Your example works fine

Re: [OMPI devel] Wtime is 0.0

That's odd; that doesn't happen to me. E.g., with this program running on MacOS 10.12.1 with Open MPI 2.0.1, I see a different value for MPI_Wtime() between successive calls: - $ cat foo.c #include #include #include int main(int argc, char *argv[]) { MPI_Init(NULL, NULL); double

[OMPI devel] Wtime is 0.0

Dear all, if have trouble with Wtime always returning 0.0 on my MacBook Pro Mac OS 10.12 openmpi 1.10.1 and 2.0.1. Wtick also returns 0.0. I this expected behaviour? Many TIA, Jan Hegewald ___ devel mailing list devel@lists.open-mpi.org https://rfd.newm

[OMPI devel] Open MPI 1.10.5rc1 is up!

An rc for the next in the v1.10.x series is available. It is unlikely that there will be many (any?) more releases after v1.10.5 -- this release is primarily because it fixes a datatype bug that is affecting applications at LANL. https://www.open-mpi.org/software/ompi/v1.10/ Changes since

Re: [OMPI devel] Open MPI v2.0.2rc1 is up

My testing is complete. The only problems not already known are related to PGI's recent "Community Edition" compilers and have been reported in three separate emails: [2.0.2rc1] Fortran link failure with PGI fortran on MacOSX [2.0.