This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
RE: [gimple] assignments to volatile
> Nathan Sidwell wrote:
>
> > RVCT generated code consistent with my proposal. Specifically in:
> > some_use_of = volatile_object = value;
> > the volatile object is only written to and not read, regardless of
> the
> > context of that volatile assignment (be it return expression,
> > conditional expression or serial assignment).
>
> Good.
>
> >> vobj;
> >> (void) vobj;
> >
> > Both of these cause a read of vobj in RVCT (and GCC).
>
> Good.
>
> If there are no objections within the next 48 hours, then I think we
> should consider the semantics settled. I'm not trying to squash
> discussion; if people don't like those semantics, let's discuss. But,
> I
> think existing practice should weigh heavily.
Agreed.
The semantics will be the same for C and C++, correct?
paul