On Fri, May 01, 2009 at 05:36:14PM -0500, James Bottomley wrote: > > OK, now I'm confused. Barriers are used to inform the compiler about > interlocks it isn't aware of (like when an asm changes a variable). The > ldcw and the *a both mention a which is sufficient an interlock for the > compiler to get it right without any barrier. > > Added to which, *a is declared volatile, which is enough of a cautionary > note to make the compiler behave in a very straightforward fashion. > I guess... I don't understand the gcc clobber semantics on asm() anymore, I'm just thinking of that stupid bug with ip_fast_csum we saw on parisc a few years ago... Don't mind me. --Kyle -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
