On Sat, 2011-02-26 at 18:12 +0000, David Brown wrote: > On Fri, Feb 25 2011, Will Deacon wrote: > > These asm blocks all have sensible looking output constraints. Why > > do they need to be marked volatile? > > Without the volatile, the compiler is free to assume the only side > effects of the asm are to modify the output registers. The volatile is > needed to indicate to the compiler that the asm has other side effects. As far as I know, volatile asm does two things: (1) It stops the compiler from reordering the asm block with respect to other volatile statements. (2) It prevents the compiler from optimising the block away when dataflow analysis indicates it's not required. If side-effects need to be indicated, won't a memory clobber do the trick? Will -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
