[OMPI users] self-messaging questions

Dear OpenMPI Pros These questions may have appeared before. Anyway, I am somewhat confused about self-messaging in MPI and OpenMPI. Questions: *1) Can a process send a message to itself?* The book "MPI: The complete reference, Vol. 1, 2nd Ed.", by Snir et al., page 42, section 2.9.9 (Comments

Re: [OMPI users] Build failure with OMPI-1.5 (clang-2.8, gcc-4.5.1 with debug options)

On Fri, Oct 15, 2010 at 01:26, Jed Brown wrote: > I'll report the bug http://llvm.org/bugs/show_bug.cgi?id=8383

Re: [OMPI users] Build failure with OMPI-1.5 (clang-2.8, gcc-4.5.1 with debug options)

Huh. Can you make V=1 to build libmpi and use the same kind of options to build your sample library? Sent from my PDA. No type good. On Oct 14, 2010, at 6:01 PM, "Jed Brown" wrote: > On Thu, Oct 14, 2010 at 23:53, Jeff Squyres wrote: > The configure test

Re: [OMPI users] Build failure with OMPI-1.5 (clang-2.8, gcc-4.5.1 with debug options)

On Oct 14, 2010, at 5:38 PM, Jed Brown wrote: > $ nm -D > /home/jed/src/openmpi-1.5/bclang/ompi/contrib/vt/vt/../../../.libs/libmpi.so > |grep MPI_Abort > 00074380 T PMPI_Abort > > In contrast, with gcc: > > $ nm -D >

Re: [OMPI users] Build failure with OMPI-1.5 (clang-2.8, gcc-4.5.1 with debug options)

On Thu, Oct 14, 2010 at 23:31, Jeff Squyres wrote: > Strange, because I see > /home/jed/src/openmpi-1.5/bclang/ompi/contrib/vt/vt/../../../.libs/libmpi.so > explicitly listed in the link line, which should contain MPI_Abort. Can you > nm on that file and ensure that it is

Re: [OMPI users] Build failure with OMPI-1.5 (clang-2.8, gcc-4.5.1 with debug options)

On Oct 14, 2010, at 5:09 PM, Jed Brown wrote: > libtool: link: clang++ -DVT_MPI -g -finline-functions -pthread -o > .libs/vtunify-mpi vtunify_mpi-vt_unify_mpi.o vtunify_mpi-vt_unify.o > vtunify_mpi-vt_unify_defs.o vtunify_mpi-vt_unify_defs_hdlr.o > vtunify_mpi-vt_unify_events.o

Re: [OMPI users] Build failure with OMPI-1.5 (clang-2.8, gcc-4.5.1 with debug options)

On Thu, Oct 14, 2010 at 22:36, Jeff Squyres wrote: > On Oct 11, 2010, at 4:50 PM, Jed Brown wrote: > > > Note that this is an out-of-source build. > > > > $ ../configure --enable-debug --enable-mem-debug > --prefix=/home/jed/usr/ompi-1.5-clang CC=clang CXX=clang++ > > $ make

Re: [OMPI users] Build failure with OMPI-1.5 (clang-2.8, gcc-4.5.1 with debug options)

On Oct 11, 2010, at 4:50 PM, Jed Brown wrote: > Note that this is an out-of-source build. > > $ ../configure --enable-debug --enable-mem-debug > --prefix=/home/jed/usr/ompi-1.5-clang CC=clang CXX=clang++ > $ make > [...] > CXXLD vtunify-mpi > vtunify_mpi-vt_unify_mpi.o: In function

Re: [OMPI users] How to time data transfers?

On 10/14/10 07:37, Jeff Squyres wrote: On Oct 13, 2010, at 4:52 PM, Michael E. Thomadakis wrote: Does MPI_Wtime of OMPI 1.4.3/1.5.0 rely on high resolution clocks (for Linux) or does still rely on gettimeofday() ? How would one request at OMPI built time to let it use high resolution

Re: [OMPI users] Problem with MPI_Comm_accept in a dynamic client/server application

Thank you for the quick response and I am looking forward to Shiqing's reply. Additionally, I noticed that I get the following warnings whenever I run an OpenMPI application. I am not sure if this has anything to do with the error that I am getting for MPI_Comm_accept: [Lazar:03288]

Re: [OMPI users] Problem with MPI_Comm_accept in a dynamic client/server application

Just FYI -- the main Windows Open MPI guy (Shiqing) is out for a little while. He's really the best person to answer your question. I'm sure he'll reply when he can, but I just wanted to let you know that there may be some latency in his reply. On Oct 13, 2010, at 5:09 PM, Kalin Kanov

Re: [OMPI users] How to time data transfers?

On Oct 13, 2010, at 4:52 PM, Michael E. Thomadakis wrote: > Does MPI_Wtime of OMPI 1.4.3/1.5.0 rely on high resolution clocks (for > Linux) or does still rely on gettimeofday() ? How would one request at OMPI > built time to let it use high resolution clocks? Check the man page for

Re: [OMPI users] Error when using OpenMPI with SGE multiple hosts

Hi, Am 14.10.2010 um 13:23 schrieb Dave Love: > Reuti writes: > >> With the default binding_instance set to "set" (the default) the >> shepherd should bind the processes to cores already. With other types >> of binding_instance these selected cores must be forward

Re: [OMPI users] Error when using OpenMPI with SGE multiple hosts

Reuti writes: > With the default binding_instance set to "set" (the default) the > shepherd should bind the processes to cores already. With other types > of binding_instance these selected cores must be forward to the > application via an environment variable or in