Lines Matching full:volatile

4 Why the "volatile" type class should not be used
7 C programmers have often taken volatile to mean that the variable could be
10 being used.  In other words, they have been known to treat volatile types
11 as a sort of easy atomic variable, which they are not.  The use of volatile in
14 The key point to understand with regard to volatile is that its purpose is
21 Like volatile, the kernel primitives which make concurrent access to data
24 need to use volatile as well.  If volatile is still necessary, there is
26 code, volatile can only serve to slow things down.
45 If shared_data were declared volatile, the locking would still be
49 volatile.  When dealing with shared data, proper locking makes volatile
52 The volatile storage class was originally meant for memory-mapped I/O
59 optimization, so, once again, volatile is unnecessary.
61 Another situation where one might be tempted to use volatile is
70 barrier, so, once again, volatile is unnecessary.  Of course, busy-
73 There are still a few rare situations where volatile makes sense in the
76   - The above-mentioned accessor functions might use volatile on
82     visible side effects, risks being deleted by GCC.  Adding the volatile
87     locking.  So jiffies can be volatile, but the addition of other
93     by I/O devices can, sometimes, legitimately be volatile.  A ring buffer
98 For most code, none of the above justifications for volatile apply.  As a
99 result, the use of volatile is likely to be seen as a bug and will bring
101 volatile should take a step back and think about what they are truly trying
104 Patches to remove volatile variables are generally welcome - as long as