Peter Zijlstra <peterz@xxxxxxxxxxxxx> writes:
Could either of you comment on the below patch? All atomic functions that return a value should imply full memory barrier semantics -- this very much includes a compiler barrier / memory clobber.
I wonder if it is possible to find a case where this makes a real difference, ie. where the compiler erroneously reused a value due to the missing barrier. Andreas. -- Andreas Schwab, schwab@xxxxxxxxxxxxxx GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
