@BRIAN_____ @johnregehr @spun_off could something else happen to the data OOO even if the code treated the pointer as volatile?
-
-
Replying to @mik235
@mik235@johnregehr @spun_off My policy is to not think about what happens when one misuses `volatile` beyond proving & removing the misuse.1 reply 0 retweets 0 likes -
Replying to @BRIAN_____
@BRIAN_____ every OS and embedded system depends on what (AFAICT) you think is misuse of volatile, right? https://lwn.net/Articles/508991/ …2 replies 0 retweets 1 like -
Replying to @johnregehr
@johnregehr If Linux were written in ISO C, that is misuse. But it is written in "the C dialect that does what Linux expects." so it's not.1 reply 0 retweets 0 likes -
Replying to @BRIAN_____
@johnregehr I think you might be arguing the "ISO C should change" perspective. I'm arguing the "let's change to cope best with ISO C" side.1 reply 0 retweets 0 likes -
Replying to @BRIAN_____
@johnregehr FWIW, I am interested in improving ISO C but improvements more likely to be adding new features, not changing existing things.1 reply 0 retweets 0 likes -
Replying to @BRIAN_____
@BRIAN_____ ISO C is frustrating, it's this fakey thing that doesn't get the job done1 reply 0 retweets 1 like
@johnregehr Sure. My goal is to minimize surprises in code I deal with, so I try to be as strict as possible. I'm no fan of ISO C. Coping.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.