alternatives to "noalias"?
Dan Bernstein
brnstnd at kramden.acf.nyu.edu
Tue Dec 11 08:09:28 AEST 1990
In article <14065 at june.cs.washington.edu> david at june.cs.washington.edu (David Callahan) writes:
> I'm not entirely sure what you mean by ``sequential dependencies''
That's exactly the problem I've been wrestling with. Wtf is a sequential
dependency? Does it mean that the result of the loop is changed if the
index goes backwards or in a random order? (This isn't good enough.)
Does it mean that no memory location accessed during the loop is written
during the loop? (This may be too restrictive, and it may not be good
enough.) What does it mean?
If the programmer writes
forall(i = 0;i < 100;i++) x[i] = y[i];
then the compiler had better be able to conclude that x and y don't
overlap. That's what we want out of the ``sequential dependency''
definition. But how can we achieve it?
Your ball.
---Dan
More information about the Comp.lang.c
mailing list