[llvm] r225159 - Fixed a bug in memory dependence checking module of loop vectorization. The following loop should not be vectorized with current algorithm.

[Chandler Carruth]

On Mon, Jan 5, 2015 at 3:08 AM, Charlie Turner <charlesturner7c5 at gmail.com>
wrote:

> Hi Jiangning,
>
> I think is causing a test failure,
>
> FAIL: LLVM :: Transforms/LoopVectorize/loop-vect-memdep.ll (10297 of 12169)
> ******************** TEST 'LLVM ::
> Transforms/LoopVectorize/loop-vect-memdep.ll' FAILED
> ********************
> Script:
> --
> /work/build-llvm-gitsvn/./bin/opt <
> /work/llvm-gitsvn/test/Transforms/LoopVectorize/loop-vect-memdep.ll -S
> -loop-vectorize -debug-only=loop-vectorize 2>&1 |
> /work/build-llvm-gitsvn/./bin/File
> Check /work/llvm-gitsvn/test/Transforms/LoopVectorize/loop-vect-memdep.ll
> --
> Exit Code: 1
>
> Command Output (stderr):
> --
> /work/llvm-gitsvn/test/Transforms/LoopVectorize/loop-vect-memdep.ll:5:10:
> error: expected string not found in input
> ; CHECK: LV: Can't vectorize due to memory conflicts
>          ^
> <stdin>:1:1: note: scanning from here
> opt: Unknown command line argument '-debug-only=loop-vectorize'. Try:
> '/work/build-llvm-gitsvn/./bin/opt -help'
> ^
> <stdin>:1:43: note: possible intended match here
> opt: Unknown command line argument '-debug-only=loop-vectorize'. Try:
> '/work/build-llvm-gitsvn/./bin/opt -help'
>                                           ^
>
> --
>
> Apologies in advance if I've messed up finding the cause of this.
>

You haven't. -debug-only isn't available in no-asserts builds and tests
*really* shouldn't rely on it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20150105/c9a3df03/attachment.html>