FreeBSD on powerpc 32 bit is moving to LLVM, so I enabled atomic.c on this platform and found it was emiting calls to make decisions about lock/lock free at runtime. We know in advance 8 byte (64 bits) operations need lock and there's no plans to create something like a "libatomic", so I creates this patch. This is being currently in use on our experimental builds/ISOs, so I ask for your inputs. Thanks!

FreeBSD on powerpc 32 bit is moving to LLVM (actually, it's now using LLVM[1] since Dec 26. I enabled atomic.c on this platform and found it was emiting calls to make decisions about lock/lock free at runtime. We know in advance 8 byte (64 bits) operations need lock and there's no plans to create something like a "libatomic", so this patch. As FreeBSD13-CURRENT ships this patch, I would like your inputs. Thanks! [1] PowerPC clang announcement - https://lists.freebsd.org/pipermail/freebsd-ppc/2019-December/011042.html

FreeBSD on powerpc 32 bit is moving to LLVM, (actually, it's now using LLVM[1] since Dec 26. so I enabled atomic.c on this platform and found it was emiting calls to make decisions about lock/lock free at runtime. We know in advance 8 byte (64 bits) operations need lock and there's no plans to create something like a "libatomic", so I createsso this patch. This is being currently in use on our experimental builds/ISOs As FreeBSD13-CURRENT ships this patch, so I ask forI would like your inputs. Thanks! [1] PowerPC clang announcement - https://lists.freebsd.org/pipermail/freebsd-ppc/2019-December/011042.html