projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 1b4a240) | patch
[LoopVectorizer] give more advice in remark about failure to vectorize call
authorSanjay Patel <spatel@rotateright.com>
Sat, 12 Jan 2019 15:27:15 +0000 (15:27 +0000)
committerSanjay Patel <spatel@rotateright.com>
Sat, 12 Jan 2019 15:27:15 +0000 (15:27 +0000)
commit7d65fe5cd55183dfed63a27f0f20e33e4b401e5b
tree7df426f87f630d41b316bbe1e3dcb47a3a93cf73tree | snapshot
parent1b4a240bfe2f548f29beec177fdc2792290872c5commit | diff
[LoopVectorizer] give more advice in remark about failure to vectorize call

Something like this is requested by:
https://bugs.llvm.org/show_bug.cgi?id=40265
...and it seems like a common enough case that we should acknowledge it.

Differential Revision: https://reviews.llvm.org/D56551

llvm-svn: 351010
llvm/lib/Transforms/Vectorize/LoopVectorizationLegality.cpp diff | blob | history
llvm/test/Transforms/LoopVectorize/libcall-remark.ll [new file with mode: 0644] blob
Domain: System / Toolchain;