search for: linearfunctiontestreplac

...most cases. I think the only flag that makes sense in SCEV is the no-wrap flag on a recurrence (that's independent of signed/unsigned overflow). As long as indvars does not rely on SCEVExpander it should be able to preserve the flags. Unfortunately, it still uses SCEVExpander in a few places. LinearFunctionTestReplace is one that should simply be moved into LSR instead. For the couple other cases, we'll just have to work on alternative implementations that don't drop flags, but I think it's worth doing. That said, we should try not to rely on NSW at all unless clearly necessary. It introduces nasty...

...ns and their original flags (and perhaps cached deduced flags)? It seems like this problem is solvable within SCEV. -Hal > > > As long as indvars does not rely on SCEVExpander it should be able to > preserve the flags. Unfortunately, it still uses SCEVExpander in a > few places. LinearFunctionTestReplace is one that should simply be > moved into LSR instead. For the couple other cases, we'll just have > to work on alternative implementations that don't drop flags, but I > think it's worth doing. > > > That said, we should try not to rely on NSW at all unless clearly...

Hi, I wanted to start a discussion about the following issue since I am not sure about what to do about it: The loop-vectorizer has the potential to make code a quite a bit bigger (esp. in cases where we don’t know the loop count or whether pointers alias). Chandler has observed this in snappy where we have a simple memory copying loop (that may overlap). We vectorize this loop and then this