Re: Number of compiler passes

George Neuner <gneuner2@comcast.net>
Sun, 03 Aug 2008 14:50:04 -0400

          From comp.compilers

Related articles
[12 earlier articles]
Re: Number of compiler passes gah@ugcs.caltech.edu (glen herrmannsfeldt) (2008-07-29)
Re: Number of compiler passes m.helvensteijn@gmail.com (Michiel) (2008-07-29)
Re: Number of compiler passes m.helvensteijn@gmail.com (Michiel) (2008-07-29)
Re: Number of compiler passes barry.kelly@codegear.com (Barry Kelly) (2008-07-30)
Re: Number of compiler passes gah@ugcs.caltech.edu (glen herrmannsfeldt) (2008-08-01)
Re: Number of compiler passes gneuner2@comcast.net (George Neuner) (2008-08-03)
Re: Number of compiler passes gneuner2@comcast.net (George Neuner) (2008-08-03)
| List of all articles for this month |
From: George Neuner <gneuner2@comcast.net>
Newsgroups: comp.compilers
Date: Sun, 03 Aug 2008 14:50:04 -0400
Organization: A noiseless patient Spider
References: 08-07-041 08-07-044 08-07-048 08-07-058 08-07-059 08-08-006
Keywords: analysis
Posted-Date: 03 Aug 2008 14:59:08 EDT

On Wed, 30 Jul 2008 17:56:11 -0700, Barry Kelly
<barry.kelly@codegear.com> wrote:


>George Neuner wrote:
>
> > Ok, we have different definitions of expression. I consider an
> > expression to compute something or cause a side effect like altering
> > control flow. To me, a variable reference like "A[X]" is a
> > subexpression that can't stand on its own.
>
>I think a symbolic location reference like A[X] is an appropriate
>structure to have in an expression tree, and that it has a type, and
>that when evaluated for computation it acts as an rvalue, but it can
>also serve as an lvalue if it occurs e.g. as the operand to an
>address-of unary expression node, or on the lhs of an assignment.


I agree that the location reference is a sub-part of an expression
tree, but I don't agree that it is an expression itself.


Anyway that is not really important. What is important is the
understanding that the notions of L-value and R-value belong to a
different abstraction level than the notions of "read-only",
"write-only" and "read/write". The OP was conflating the concepts and
I was attempting to correct his misinterpretation.


George


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.