[Pkg-openmpi-maintainers] [OMPI devel] Build failures of 1.2.3 on Debian hppa, mips, mipsel, s390, m68k
Brian Barrett
bbarrett at lanl.gov
Sat Jul 14 17:59:23 UTC 2007
On Jul 14, 2007, at 11:51 AM, Gleb Natapov wrote:
> On Sat, Jul 14, 2007 at 01:16:42PM -0400, George Bosilca wrote:
>> Instead of failing at configure time, we might want to disable the
>> threading features and the shared memory device if we detect that we
>> don't have support for atomics on a specified platform. In a non
>> threaded build, the shared memory device is the only place where we
>> need support for memory barrier. I'll look in the code to see why we
>> need support for compare-and-swap on a non threaded build.
> Proper memory barrier is also needed for openib BTL eager RDMA
> support.
Removed all the platform lists, since they won't care about this
part :).
Ah, true. The eager RDMA code should check that the preprocessor
symbol OPAL_HAVE_ATOMIC_MEM_BARRIER is 1 and disable itself if that
isn't the case. All the "sections" of ASM support (memory barriers,
locks, compare-and-swap, and atomic math) have preprocessor symbols
indicating whether support exists or not in the current build. These
should really be used :).
Brian
More information about the Pkg-openmpi-maintainers
mailing list