Displaying 2 results from an estimated 2 matches for "d55288".
Did you mean:
d35288
2019 Oct 02
2
vectorize.enable
...ot;the optimizer was unable to perform the requested transformation". We could argue about the suggestions given as to why the transformations didn't happen in this case, but overall I think this is an improvement.
The patch that added the warning as-is was by me
(https://reviews.llvm.org/D55288). It changed to emitted message from
"loop not vectorized: failed explicitly specified loop vectorization"
to the lengthier description following review feedback.
It's done by the WarnMissedTransformation and just looks for
transformation metadata that is still in the IR after all pa...
2019 Oct 02
2
vectorize.enable
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