| |||||||||||||
ACCESS_ONCE()ACCESS_ONCE()Posted Aug 13, 2012 8:02 UTC (Mon) by jezuch (subscriber, #52988)In reply to: ACCESS_ONCE() by daglwn Parent article: ACCESS_ONCE()
> C compilers detect it all the time. It is a trivial analysis. Users tend to ignore the warnings, however.
It is. And they do. And every time I see someone fixing a "use of undefined variable" warning by initializing it to zero at declaration point, I cringe. I've seen it in stable updates to the kernel a lot...
(Log in to post comments)
ACCESS_ONCE() Posted Aug 13, 2012 16:31 UTC (Mon) by daglwn (subscriber, #65432) [Link]
Absolutely. One needs to first understand _why_ the warning is there before fixing it. Warnings don't replace understanding.
|
|||||||||||||