GCC not (optimally) exploiting restrict pointers?

[Steven Bosscher]

On Wednesday 15 December 2004 18:10, Dave Korn wrote:
> .... unless of course b was derived from a in the function that calls
> foo(), perhaps?

Not sure.  See http://gcc.gnu.org/ml/gcc-patches/2004-08/msg00246.html
for a similar example of the semantics of restrict.

I think Richard is right and we can do this transformation even if b is
not restrict, but I'm not sure - this stuff is over my head...  :-/

Gr.
Steven