Fwd: OpenPA atomic primitives
any takers? Context is lam4 deprecation, and both alternatives
FTBFS on m68k due to missing arch-specific locks handling.
mpich2 is supposed to be more portable.
#3 sounds to be the “best” one, #2 the fallback I could do
when nobody does #3…
“Having a smoking section in a restaurant is like having
a peeing section in a swimming pool.”
-- Edward Burr
---------- Forwarded message ----------
From: Pavan Balaji <firstname.lastname@example.org>
Date: Mon, 26 Dec 2011 02:57:50 -0600
Subject: OpenPA atomic primitives
There are three possible solutions for this:
1. You can disable OPA's processor atomics using --with-atomic-primitives=no as
the configure error message states. In this case, OPA will use locks to emulate
atomic operations, which is slower but works correctly.
2. You can change the device to ch3:sock (using the configure option
--with-device=ch3:sock), which doesn't use shared memory at all and hence
doesn't need OPA atomics.
3. You can contribute m68k processor atomics to OPA, so it is natively supported
and OPA doesn't have to fall back to locks.