Re: why are some atomic_t's not volatile, while most are?

[Chris Friesen]

Jan Engelhardt wrote:
> On Aug 7 2007 15:38, Chris Friesen wrote:

> > That volatile is there precisely to force the compiler to dereference it every
> > single time.

> Actually, the dereference will be done once (or more often if registers
> are short or the compiler does not feel like keeping it around),
> and the read from memory will be done on every iteration ;-)

My bad.  You are, of course, correct.  :)

Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/