Another question can be asked (or simply another way to look at the original question):
Does making a struct const make all its members const?
If I have:
struct whatever { int data; };
const whatever test;
Will test.data be const too?
My answer is : Yes. If you declare an object of type whatever with const then all its members will be const too
Similarly, if you declare an object of type whatever with volatile then all its members will be volatile too, just like if you declare the object with const, all it’s member will be const too.
const and volatile are two faces of the same coin; they’re so that the Standard often refers to them as cv-qualifiers.
Quoting from the Standard ($7.1.5.1/8)
[Note: volatile is a hint to the
implementation to avoid aggressive
optimization involving the object
because the value of the object might
be changed by means undetectable by an
implementation. See 1.9 for detailed
semantics. In general, the semantics
of volatile are intended to be the
same in C + + as they are in C. ]
That means, if your object is an instance of a struct, then the compiler cannot avoid aggressive optimization involving the object, unless it avoids aggressive optimization of each of it’s members. (Otherwise, how else it can avoid optimization involving the object?)
Related topic:
Why do we use volatile keyword in C++?