"hostfile" to the more conforming name "llm_hostfile_hostfile".
The shortcut for hostfile-selection with -hostfile, e.g.:
mpirun -np 98234 -hostfile big_machine ./test
still works.
This commit was SVN r4233.
running on hardware with such support. Since the calling convention is
to use the registers as 32 bit values (even if they are 64 bit registers),
we need to pack things up properly before doing the compare and set.
This commit was SVN r4226.
libraries. So if we fail to find a symbol in the vapi library, try
looking for -lpthread, and if that succeeds, then try looking for a
second symbol in the vapi library.
This especially happens if you use Mellanox v3.1 and --without-threads
in the top-level configure.
This commit was SVN r4201.
during testing. In particular, we can't have a cmpset macro that can
deal with pointers without some really evil voodoo. So have a
different macro for pointers
* Add more detailed testing of the atomics using AM's test framework.
More to come...
This commit was SVN r4191.
of assembler format
* Fix minor bugs in AMD64, PPC, and IA32 assembly for atomic operations
* Clean up the #defines to look for when examining level of atomic operation
support
This commit was SVN r4183.
after MPI-startup.
For this a new mpirun-parameter "mpi_signal" is added, one may specify a
comma-separated list of signals to grab, e.g. mpirun --mca mpi_signal 8,11
will check for SIGFPE and SIGSEGV.
It only finds the first fault (SA_ONESHOT), as after the return the same
fault will occur again.
As printout, the data provided by siginfo_t is printed to STDOUT (yes,
it calls printf ,-]).
Additionally, with glibc, it uses backtrace and backtrace_symbols to
print the calling stack up to the function in which the signal was raised:
(Rank:0) Going to write to RD_ONLY mmaped shared mem
Signal:11 info.si_errno:0(Success) si_code:2(SEGV_ACCERR)
Failing at addr:0x4020c000
[0] func:/home/rusraink/ompi-gcc/lib/libmpi.so.0 [0x40121afe]
[1] func:./t0 [0x42029180]
[2] func:./t0(__libc_start_main+0x95) [0x42017589]
[3] func:./t0(__libc_start_main+0x49) [0x8048691]
This commit was SVN r4170.
from themselves -- but doesn't look valid. For example, it's legal to
have $FC and $F77 to both be ifort (intel fortran compiler).
This commit was SVN r4148.
removing mpga.h include as it breaks in the latest Mellanox VAPI releases (actually, mpga.h
is moved to mpga/mpga.h...yuck!)
This commit was SVN r4146.
