search for: 858a1ae

Hi Michael and Florian, ( + llvm-dev for visibility) I would like to quickly follow up on "Pragma vectorize_width() implies vectorize(enable)", which got reverted with commit 858a1ae for 2 reasons, see also that revert commit message. Ignore the assert, that's been fixed now. The other thing is that with the patch behaviour is slightly changed and we could get a diagnostic we didn't get before: warning: loop not vectorized: the optimizer was unable to perform th...

...ng: loop not vectorized: the optimizer was unable to > perform the requested transformation; the transformation might be disabled or > specified as part of an unsupported transformation ordering > [-Wpass-failed=transform-warning] > > For the example given in revert 858a1ae, in both cases before and after my commit, the loop vectoriser was bailing because "Not vectorizing: The exiting block is not the loop latch". The source looks like a straightforward canonical loop. What pass transformed it to have code between the exiting block and the latch? > But...