I'm working on some intercommunicator stuff at the moment. According to
MPI-2.2 standard:
"An inter-communication is a point-to-point communication between
processes in different groups" [Section 6.6]
yet the "man" page for MPI_Comm_size reads:
"If the communicator is an **intra-communicator
Following the discussion about ABI compatibility and type-punning of non
client-visible types, I've attached a patch against 1.3.2 which casts to
an opaque (void *) when OMPI_BUILDING is 0.
This will prevent the compiler from trying to do any strict-aliasing
based optimizations when the defini
Many thanks for the informative explanation, Jeff. I appreciate this
issue has been the cause of some deliberation!
This was the changeset where we did the ABI fixes -- ensuring that if
you compile/link against Open MPI vA.B.C, you will be able to just
change your LD_LIBRARY_PATH or replace
Christian Siebert wrote:
Hi Number Cruncher,
With, or without, C++ bindings, I'm getting serious warnings when
compiling *any* C++ program which #includes :
that's one of the many reasons why the C++ bindings will very likely be
removed in the next version of the MPI standa
With, or without, C++ bindings, I'm getting serious warnings when
compiling *any* C++ program which #includes :
Program (helloMPI.cpp):
#include
#include
int
main(int argc, char *argv[])
{
MPI_Init(&argc, &argv);
int myRank;
if(!MPI_Comm_rank(MPI_COMM_WORLD, &myRank)) {
std::cout <<
Although --enable-mem-debug resolves the issue, I get warnings about
uninitialized bytes in writev from the opal_if_t structs in opal_ifinit:
==25777== Syscall param writev(vector[...]) points to uninitialised byte(s)
==25777==at 0x34DE2C9F0C: writev (in /lib64/libc-2.6.so)
==25777==by 0
I couldn't get Open MPI 1.3 to compile on RedHat 9 or CentOS3, due to
vt_unify_stats.h using the tolower() function without including the
relevant header.
Attached is patch against 1.3 release to fix this minor bug.
diff -r -U 5 openmpi-1.3.orig/ompi/contrib/vt/vt/tools/vtunify/vt_unify_stats.h
