|author||Rich Felker <firstname.lastname@example.org>||2014-07-19 18:23:24 -0400|
|committer||Rich Felker <email@example.com>||2014-07-19 18:23:24 -0400|
fix microblaze atomic store
as far as I can tell, microblaze is strongly ordered, but this does not seem to be well-documented and the assumption may need revisiting. even with strong ordering, however, a volatile C assignment is not sufficient to implement atomic store, since it does not preclude reordering by the compiler with respect to non-volatile stores and loads. simply flanking a C store with empty volatile asm blocks with memory clobbers would achieve the desired result, but is likely to result in worse code generation, since the address and value for the store may need to be spilled. actually writing the store in asm, so that there's only one asm block, should give optimal code generation while satisfying the requirement for having a compiler barrier.
Diffstat (limited to 'arch/microblaze')
1 files changed, 3 insertions, 1 deletions
diff --git a/arch/microblaze/atomic.h b/arch/microblaze/atomic.h
index 90fcd8b6..da9949aa 100644
@@ -95,7 +95,9 @@ static inline void a_dec(volatile int *x)
static inline void a_store(volatile int *p, int x)
+ __asm__ __volatile__ (
+ "swi %1, %0"
+ : "=m"(*p) : "r"(x) : "memory" );
static inline void a_spin()