On 07/22/2013 10:30 PM, pdziepak-github.lock_elision wrote:
+/* int64 atomic_get64_aligned(vint64 *value) */ +FUNCTION(atomic_get64_aligned):
Is there any reason you introduce new functions for this? Just let the old ones panic with non-aligned values. BeOS only had atomic_or() and atomic_and(), but there is really little reason to support this; if there is really a driver from back then we wanted to use, the chance it uses unaligned atomics is pretty small.