[PATCH] D62997: [LV] Share the LV illegality reporting with LoopVectorize. NFC.

[Hideki Saito via Phabricator via llvm-commits]

hsaito added a comment.

Looking at the expected output and the explanations on -Rpass* flags, it could be that those tests should be using -pass-remarks-analysis=loop-vectorize, instead of -pass-remarks-missed=loop-vectorize. Would you try?

In D62997#1557206 <https://reviews.llvm.org/D62997#1557206>, @psamolysov wrote:

> @hsaito
>
> Here is the log of lit on Vectorization:
>
> - Testing: 319 tests, 8 threads -- Testing: 0 .. 10.. 20.. 30.. 40. FAIL: LLVM :: Transforms/LoopVectorize/control-flow.ll (150 of 319)
>   - TEST 'LLVM :: Transforms/LoopVectorize/control-flow.ll' FAILED ******************** Script: -- : 'RUN: at line 1';   bin\opt.exe < llvm\test\Transforms\LoopVectorize\control-flow.ll -loop-vectorize -force-vector-width=4 -S -pass-remarks-missed='loop-vectorize' 2>&1 | bin\filecheck.exe llvm\test\Transforms\LoopVectorize\control-flow.ll




--------------------------------------

Snippet from https://llvm.org/docs/Vectorizers.html:

Many loops cannot be vectorized including loops with complicated control flow, unvectorizable types, and unvectorizable calls. The loop vectorizer generates optimization remarks which can be queried using command line options to identify and diagnose loops that are skipped by the loop-vectorizer.

Optimization remarks are enabled using:

-Rpass=loop-vectorize identifies loops that were successfully vectorized.

-Rpass-missed=loop-vectorize identifies loops that failed vectorization and indicates if vectorization was specified.

-Rpass-analysis=loop-vectorize identifies the statements that caused vectorization to fail. If in addition -fsave-optimization-record is provided, multiple causes of vectorization failure may be listed (this behavior might change in the future).


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D62997/new/

https://reviews.llvm.org/D62997