[PATCH] D10714: Modify interleave diagnostics to clearly indicate why interleaving wasn't done.

Gerolf Hoflehner ghoflehner at apple.com
Fri Jul 10 14:14:41 PDT 2015


Gerolf added inline comments.

================
Comment at: lib/Transforms/Vectorize/LoopVectorize.cpp:1575
@@ -1574,3 +1574,3 @@
     if (Hints.getWidth() == 1 && Hints.getInterleave() == 1) {
       DEBUG(dbgs() << "LV: Not vectorizing: Disabled/already vectorized.\n");
       emitOptimizationRemarkAnalysis(
----------------
The comment in DEBUG ('already vectorized') is inconsistent with your comment.

================
Comment at: lib/Transforms/Vectorize/LoopVectorize.cpp:1578
@@ -1577,3 +1577,3 @@
           F->getContext(), DEBUG_TYPE, *F, L->getStartLoc(),
-          "loop not vectorized: vector width and interleave count are "
-          "explicitly set to 1");
+          "loop not vectorized: vectorization and interleaving are explicitly "
+          "disabled, or vectorize width and interleave count are both set to "
----------------
Could there be two separated remarks something like a) not vectorized because turned off and b) not vectorized because of low thresholds


http://reviews.llvm.org/D10714







More information about the llvm-commits mailing list