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
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
On Fri, Oct 15, 2010 at 00:38, Jeff Squyres (jsquyres)
wrote:
> Huh. Can you make V=1 to build libmpi and use the same kind of options to
> build your sample library?
>
Make log here
http://59A2.org/files/openmpi-1.5-clang-make.log
After some digging, this looks like a clang bug. First, from t
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 essentially looks like this -- could
On Thu, Oct 14, 2010 at 23:53, Jeff Squyres wrote:
> The configure test essentially looks like this -- could you try this
> manually and see what happens?
>
> cat > conftest_weak.h < int real(int i);
> int fake(int i);
> EOF
>
> cat > conftest_weak.c < #include "conftest_weak.h"
> #pragma weak fa
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
> /home/jed/src/openmpi-1.5/bgcc/ompi/contrib/vt/vt/../../../.libs/li
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 actually listed there?
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 vtunify_mpi-vt_u
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
> > [...]
> > CXXLD
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 `VTUnify_M
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 clocks
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] mca_oob_
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 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 clocks?
Check the man page for MPI_Wtime(3
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 to the
>> application via an e
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 the hostfile.
My question was
On Oct 12, 2010, at 2:04 PM, gaurav bhatnagar wrote:
> I am trying to install openmpi 1.4.1 on my cluster with linux ( RH EL 3 upd 3
> ).
> I want to run Ls dyna job on cluster, but it showed error as some files are
> missing.
> I also tried to copy shared lib files from ls dyna but then open mp
17 matches
Mail list logo
