This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: objects_must_conflict_p
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: ebotcazou at libertysurf dot fr
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 5 Jul 03 09:51:14 EDT
- Subject: Re: objects_must_conflict_p
Then a (non-temporary) 'struct a_iterator1' object is created:
allocated on the stack and constructed, so 'adaptor' is
assigned. 'struct iterator1' and 'struct a_iterator1' conflicts
according to objects_must_conflict_p, because the latter is a
supertype of the former.
Yuck! It looks like we have to say they only are guaranteed to conflict
if they have the *same* alias set.