This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Volatile MEMs in statement expressions and functions inlinedastrees
- From: Jason Merrill <jason at redhat dot com>
- To: Paul Schlie <schlie at mediaone dot net>
- Cc: Alexandre Oliva <aoliva at redhat dot com>, Richard Henderson<rth at redhat dot com>, <gdr at codesourcery dot com>, Aldy Hernandez <aldyh at redhat dot com>, <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 07 Jan 2002 21:09:29 +0000
- Subject: Re: Volatile MEMs in statement expressions and functions inlinedastrees
- References: <B85F777C.378C%schlie@mediaone.net>
>>>>> "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