installed copy, it
successfully removes the warnings.
-- Jeremiah Willcock
ble_platform.h:377:34: warning: invalid suffix on literal;
C++11 requires a space between literal and string macro [-Wliteral-suffix]
_STRINGIFY(__GNUC__)"."_STRINGIFY(__GNUC_MINOR__)".?"
The fix is to insert spaces between the strings like the warnings say;
doing that is compatible with both older and new language standards.
-- Jeremiah Willcock
systems. You might want to try commenting out the entire body of
win_compat.h and re-enabling only those parts that are truly necessary
(and don't have MinGW headers that should be used instead, such as for
ssize_t).
-- Jeremiah Willcock
On Tue, 20 Aug 2013, Richard Haney wrote:
Ah! Thanks, Jeff
re issue (detecting your
architecture as IA-32 and not x86-64), not a problem in the assembly files
themselves.
-- Jeremiah Willcock
ars to be poorly documented in general
(mentioned in ompi_info -a and on the mailing lists), and seems like it
would be an incredibly useful debugging tool when running a crashing
application under a debugger.
-- Jeremiah Willcock
code
work (since the datatype is actually contiguous).
-- Jeremiah Willcock
On Tue, 25 Sep 2012, Ralph Castain wrote:
IIRC, we found a configure "bug" that allowed you to enable-memchecker without
also including the required --with-valgrind. You might try again with 1.6.2, which
. The configure flags I used to
build Open MPI were a prefix and:
--disable-pretty-print-stacktrace --enable-mpi-thread-multiple
--enable-memchecker --enable-mca-no-build=btl-openib --enable-debug
and I am using GCC 4.7.1 on Linux. Is this a known issue? Thank you for
your help.
-- Jeremiah
standard that says either way whether this is allowed.
-- Jeremiah Willcock
I think MPI should also provide that way. May be it is
not in my knowledge. That's why I am asking the experts. I am still
looking for it :(
-- Jeremiah Willcock
coordinates to rank.
-- Jeremiah Willcock
n 0;
}
produces an infinite loop in MPI_Waitall. Running under valgrind, the
MPI_Waitall call produces a NULL pointer dereference and thus a
segmentation fault. The code works correctly in Open MPI 1.4.1 and in
1.5.1 when using the TCP BTL.
-- Jeremiah Willcock
I forgot to mention that this was tested with 3 or 4 ranks, connected via
TCP.
-- Jeremiah Willcock
On Thu, 10 Feb 2011, Jeremiah Willcock wrote:
Here is a small test case that hits the bug on 1.4.1:
#include
int arr[1142];
int main(int argc, char** argv) {
int rank, my_size;
MPI_Init
();
return 0;
}
I tried it on 1.5.1, and I get MPI_ERR_TRUNCATE instead, so this might
have already been fixed.
-- Jeremiah Willcock
On Thu, 10 Feb 2011, Jeremiah Willcock wrote:
FYI, I am having trouble finding a small test case that will trigger this on
1.5; I'm either getting deadlocks
it.
-- Jeremiah Willcock
On Thu, 10 Feb 2011, Jeff Squyres wrote:
Nifty! Yes, I agree that that's a poor error message. It's probably
(unfortunately) being propagated up from the underlying point-to-point system,
where an ERR_IN_STATUS would actually make sense.
I'll file a ticket about
On Wed, 9 Feb 2011, Jeremiah Willcock wrote:
I get the following Open MPI error from 1.4.1:
*** An error occurred in MPI_Bcast
*** on communicator MPI COMMUNICATOR 3 SPLIT FROM 0
*** MPI_ERR_IN_STATUS: error code in status
*** MPI_ERRORS_ARE_FATAL (your MPI job will now abort)
(hostname
). There is no MPI_Status
returned by MPI_Bcast, so I don't know what the error is? Is this
something that people have seen before?
-- Jeremiah Willcock
otherwise?
-- Jeremiah Willcock
In the online man page for this function, MPI_MODE_SEQENTIAL should be
MPI_MODE_SEQUENTIAL. Also,
http://www.open-mpi.org/doc/v1.4/man3/MPI_File_open.3.php is showing man
page source code rather than the rendered text.
-- Jeremiah Willcock
The "WHEN COMMUNICATOR IS AN INTER-COMMUNICATOR" section in the man page
for MPI_Allreduce (in both 1.4.1 and the current SVN trunk) mentions the
use of a root process and a "root" parameter name (which doesn't exist for
MPI_Allreduce). Should I add this to Trac?
-- Jeremiah Willcock
that there
is an easy way to get just the flags that OMPI_LIBS contains by default
(either using -showme:link or ompi_info). Is there a way to add to the
default set of OMPI_LIBS rather than overriding it entirely? Thank you
for your help.
-- Jeremiah Willcock
er.
"""
I believe "exit" there should be "exist".
-- Jeremiah Willcock
21 matches
Mail list logo
