volatile [was: GCC warnings for unused global variables]

[Mike Stump]

On Tuesday, May 6, 2003, at 09:03 PM, Alexandre Oliva wrote:
> On May  7, 2003, Michael Eager <eager@eagercon.com> wrote:
>
>> If you take the view that "a <op>= b" involves a read and a write, 
>> then
>> translating it into load/operate/store is correct.
>
> But then, so is a single instruction that loads, operates then stores,
> right?  The thing is that GCC doesn't ever give such instruction a
> chance if the variable is volatile.

But, obviously, it should be made to.  No one has bothered in getting 
it into the compiler, yet.