🚀 go-pugleaf

In article <5853:Nov720:22:4890@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:

>Here is a very precise description of how a C compiler can detect the
>sort of non-aliasing that a Fortranish program has.

[ description deleted ]

Your description doesn't seem to work for Fortran-style aliasing. You
can't just test the starting address of an array; you must consider
the set of all addresses in the arguments which are changed by any
actual control path through the subroutine. Your example was worked
out with 3 scalar arguments. If I were a CS type, I'd probably think
the array case was pretty nasty to solve.

example: from my reading of the standard, this is valid:

      real a(10)
      call foo(a,a(3))
      ...
      subroutine foo(x,y)
      real x(3), y(7)
      x(2) = 1.0
      y(2) = 1.0

x(3) overlaps with y(1), yet since neither x(3) nor y(1) is written by
the routine, the anti-aliasing rule holds. Determining the set of all
addresses written by a subroutine with all sorts of data-dependent
branches is not fun.

Now, hit 'n' because the interesting part of this posting is over.

More quotes from the Dan Bernstein quote collection, all of these
aimed at Jim:

>Jim, please say *something* that shows you understand the above
>description.

>Now for the seventh or eighth time, here's how it applies to the
>three-file case above:

>I am getting really, really, really sick of trying to explain this to
>you; I hope my excessively detailed and formal approach here does the
>job. I will give up if you persist in ignoring the truth.

> You are becoming a bit repetitive.

>Sir, you appear to be lying. But I've promised myself not to drag you
>over the coals for your repeated misquotes, misparaphrases, misleading,
>and apparent outright lies.

And, in a different posting, Dan said to me:

> Weird, you're right.

Dan, I expect these sorts of lines in alt.flame, but not
comp.lang.misc.