🚀 go-pugleaf

In article <1990Aug9.174513.16437@rice.edu> preston@titan.rice.edu (Preston Briggs) writes:
>(Apparently, in the case of C, the optimizer is allowed to
>do anything, since expressions with side effects are undefined(!).
>Remember that "undefined" means the optimizer may fork a game of
>chess if it cares to.).

Huh?  Do you know C?   Of course expressions with side-effects are
defined.  Where there is *more than one* side effect, the rules are a
little loose on which side effect gets evaluated first.  Not unclear,
but clearly undefined.  However, there are many situations where the
order of side effects *is* defined: for example, all side-effects in
arguments to a function are finished before the function is called.
However, if you say something like (a[i++] = i), the order of
evaluation can change. The compiler may index a with i, add one to i,
and then assign the new i to a[i]; or it may index a with i, add one to
i, and then assign the old i to a[i]; depending on registers available,
optimizations, and so on. Changing a value and using it in the same
expression (except for some very explicit operators) has always been a
no-no in C.  Such expressions have always been illegal; sadly, most
compilers don't seem to bother to check for illegal programs if they
can compile them into *something*.  I don't know: does lint?

(Also, I don't think there is much use in forking a chess game, either
in the optimizer *or* in the optimized code. "Undefined" does not mean
"silly" :-).

			  -- Darren