Posted Aug 13, 2012 16:34 UTC (Mon) by daglwn (subscriber, #65432)
In reply to: ACCESS_ONCE() by etienne
Parent article: ACCESS_ONCE()
It is not trivial to get an exact and accurate answer in the general case, true, but I was assuming we were talking about the common case of locally-declared variables.
Still, even in this case the compiler could warn about it even if it doesn't know for sure. The code certainly looks suspicious and a warning would be appropriate. False positives are just fine if they are limited in number. The compiler can provide directives to suppress them if the programmer knows it's not a problem.
Note that gcc does just this. It warns that variables *might* be uninitialized.