🚀 go-pugleaf

From article <7177:Nov620:48:1590@kramden.acf.nyu.edu>, by brnstnd@kramden.acf.nyu.edu (Dan Bernstein):
> [... if-test around aliased vs. non-aliased code ...]
> However, a smart compiler can perform this optimization automatically. In
> most cases it can do the test at compile time, and generate calls to
> either the fast compiled version or the slow compiled version. I don't
> know why Jim repeatedly insists this is impossible.

The example given doesn't even contain a procedure call.  It has
nothing at all to do with the thing that I consistently have asserted
is not possible for the compiler _alone_.  As it happens, I agree that
this case probably has a purely compile-time (or compiled-in run-time)
solution.

It is you continued claim that the compiler can solve interprocedural
aliasing questions by itself (and at compile-time) that I disagree with.

J. Giles