diff options
| author | Adam Nemet <anemet@apple.com> | 2016-11-11 22:51:46 +0000 |
|---|---|---|
| committer | Adam Nemet <anemet@apple.com> | 2016-11-11 22:51:46 +0000 |
| commit | 9bfbf8bbdfda79210b4f37d0431151d359a0ee9b (patch) | |
| tree | 210be32745d60d56064555fc84cc32ada094e67a /llvm/lib/Transforms | |
| parent | 720a20a26bbabbd7c6a785f3f69bba67c4ca081f (diff) | |
| download | bcm5719-llvm-9bfbf8bbdfda79210b4f37d0431151d359a0ee9b.tar.gz bcm5719-llvm-9bfbf8bbdfda79210b4f37d0431151d359a0ee9b.zip | |
[LV] Stop saying "use -Rpass-analysis=loop-vectorize"
This is PR28376.
Unfortunately given the current structure of optimization diagnostics we
lack the capability to tell whether the user has
passed -Rpass-analysis=loop-vectorize since this is local to the
front-end (BackendConsumer::OptimizationRemarkHandler).
So rather than printing this even if the user has already
passed -Rpass-analysis, this patch just punts and stops recommending
this option. I don't think that getting this right is worth the
complexity.
Differential Revision: https://reviews.llvm.org/D26563
llvm-svn: 286662
Diffstat (limited to 'llvm/lib/Transforms')
| -rw-r--r-- | llvm/lib/Transforms/Vectorize/LoopVectorize.cpp | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/llvm/lib/Transforms/Vectorize/LoopVectorize.cpp b/llvm/lib/Transforms/Vectorize/LoopVectorize.cpp index 2c43a5679e4..abbe416179c 100644 --- a/llvm/lib/Transforms/Vectorize/LoopVectorize.cpp +++ b/llvm/lib/Transforms/Vectorize/LoopVectorize.cpp @@ -1319,8 +1319,7 @@ public: else { OptimizationRemarkMissed R(LV_NAME, "MissedDetails", TheLoop->getStartLoc(), TheLoop->getHeader()); - R << "loop not vectorized: use -Rpass-analysis=loop-vectorize for more " - "info"; + R << "loop not vectorized"; if (Force.Value == LoopVectorizeHints::FK_Enabled) { R << " (Force=" << NV("Force", true); if (Width.Value != 0) |

