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 inlined as trees
- From: Gabriel Dos Reis <gdr at codesourcery dot com>
- To: Linus Torvalds <torvalds at transmeta dot com>
- Cc: Richard Henderson <rth at redhat dot com>, Alexandre Oliva <aoliva at redhat dot com>, <gdr at codesourcery dot com>, <gcc-patches at gcc dot gnu dot org>
- Date: 13 Dec 2001 23:27:59 +0100
- Subject: Re: Volatile MEMs in statement expressions and functions inlined as trees
- Organization: CodeSourcery, LLC
- References: <Pine.LNX.4.33.0112131338240.1851-100000@penguin.transmeta.com>
Linus Torvalds <torvalds@transmeta.com> writes:
[...]
| My argument is a consistency argument,
Now, the line of your reasoning moved to what *you* think the
behaviour should be, not something backed up by a formal text. That
is then another debate.
| where one of the corner stones is
| exactly the fact that _because_ "p = 0" does not load from memory, then "q
| = p = 0" should _also_ not load.
|
| So I'm asking for _consistency_, nothing more.
>From consistency point of view, the handling of the above should be
consistent with
q = p;
[...]
| I'm also claiming that the C++ standard does _not_ require the
| "lvalue->rvalue" conversion to be a dereference, but does, in fact, quite
| clearly allow it to be just the value assigned.
You didn't show anything to that effect backed up by a text from C++
definition. What you show is your personnal view.
-- Gaby