Volatile MEMs in statement expressions and functions inlined astrees

[Jason Merrill]

>>>>> "Paul" == Paul Schlie <schlie@mediaone.net> writes:

> As a minor correction, to what about volatile x; or *p;, it would seem to be
> the case that if a volatile *p were to be evaluated in an <lvalue> context,
> it should likely require a dereference access of *p, sorry for my likely too
> quick earlier response.

I don't think so.  The dereference is implied by the lvalue-to-rvalue
conversion.

Jason