On Tue, 16 Sep 2003, Ph. Marek wrote:
> > You can, of course, stop even potential optimization once the first "I can
> > change the rules" operation is found, but since even assignment can change
> > the rules that's where we are right now. We'd like to get better by
> > optimizing based on what we can see at compile time, but that's a very,
> > very difficult thing to do.
> How about retaining some "debug" info, (line number come to mind), but only at
> expression level??
This is insufficient, since many (potentially most) optimizations result
in reordered, refactored, moved, and/or mangled code that doesn't have a
line-for-line, or expression-for-expression, correspondence to the
original. If it did, this would all be much easier.
The alternative, of course, is to not apply those transforms, but then
you're left with pretty much no optimizations.
Dan
