On 12/18/2012 02:52 PM, Ian Lance Taylor wrote: > Argh. But why? Wouldn't that only apply to cases where the lock was > sometimes locked by one library and sometimes locked by a different > one?
Or did you really mean "... only apply to cases where the memory protected by the lock was visible to more than one library." Yes, if libgo is attempting atomic accesses to its own data structures, which themselves are not exported from libgo, then a copy of libatomic ought to work. It would probably be better for the shared libgo to depend on the shared libatomic though. That's simply more pedantically correct. r~
