Rich Felker ea818ea834 add working a_spin() atomic for non-x86 targets ...

conceptually, a_spin needs to be at least a compiler barrier, so the
compiler will not optimize out loops (and the load on each iteration)
while spinning. it should also be a memory barrier, or the spinning
thread might keep spinning without noticing stores from other threads,
thus delaying for longer than it should.

ideally, an optimal a_spin implementation that avoids unnecessary
cache/memory contention should be chosen for each arch, but for now,
the easiest thing is to perform a useless a_cas on the calling
thread's stack.

2014-08-25 15:43:40 -04:00

..

bits

…

src

…

atomic.h

add working a_spin() atomic for non-x86 targets

2014-08-25 15:43:40 -04:00

crt_arch.h

…

pthread_arch.h

…

reloc.h

…

syscall_arch.h

…