On Fri, Apr 08, 2005 at 10:52:02AM -0600, Jeffrey A Law wrote: > It would probably be wise to audit the other uses of > copy_virtual_operands. We might also consider forcing statement > rescans as part of our IL checking code to avoid these kinds of > problems in the future. > Yes, I've run into this problem and am about to commit fixes in this area.
Both ivopts and the vectorizer were creating bad memory tags for the new pointers. Also, after ivopts, the whole CFG needs to be re-scanned because the new alias relations it creates affect statements that have not even been modified by the process. Something similar happens with aliasing, after the alias pass we're force to rescan just about every statement in the CFG. Such contortions are not going to be needed so frequently as we improve the aliasing code (hopefully). Diego.
