gcc3 vs 176.gcc

[Hartmut Schirmer]

On Wednesday, January 09, 2002 7:09 PM, Dale Johannesen wrote
[...]
> Having thought about it more, I now think gcc3's behavior in this
> case is clearly wrong, at least as a quality-of-implementation issue.
> The aliasing rules are there to permit compilers to make aggressive
> assumptions when they can't tell whether two memrefs alias or not.
> They are not there to permit compilers to do stupid things when they
> can easily tell that two memrefs do alias.  The examples in the
> Rationale make this clear.

True. And it's not fair to tell the Linux folks the compiler will
look through cast in one case abd doesn't do so in other cases ...

GCC should behave a little more predictable here.

Hartmut