This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: aggregate aliasing losage
- To: rth at cygnus dot com
- Subject: Re: aggregate aliasing losage
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Date: Thu, 1 Jun 00 19:41:21 EDT
- Cc: gcc-patches at gcc dot gnu dot org
] 7 An object shall have its stored value accessed only by an lvalue
] expression that has one of the following types:
] - a type compatible with the effective type of the object,
the type of `b->d' is certainly compatible with the type of `a->d',
which is the object being referenced.
Hmm... that's certainly true.
Let me go back and remember why it was necessary to have the alias set be
the whole structure, but I know it was.
A way to fix this would be to go back to what the original comments said (but
code never did) and consider two alias set conflicting if any descendant
are the same. The reason I don't like that is that it basically makes any
two structures alias each other in practice.