hsaito added a comment. There are two ways to think.
1. vectorize(disable) as in disable the LoopVectorize pass itself. 2. vectorize(disable) as in disabling the loop vectorization transformation It all depends on to whom we are providing these pragmas. If we are providing pragmas for programmers, they don't care LoopVectorize or something else. They care about vectorization of loop. So, 2) makes more sense. If we are providing pragmas for compiler writers, we should be making this more like #pragma clang loop LoopVectorize(disable) so that what is controlling what crisply known to everyone. For anything that is programmer visible, I think it's time for LLVM vectorizer to focus on how the programmers use rather than how vectorizer writers think about things. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D66796/new/ https://reviews.llvm.org/D66796 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits