From cf3b5559739576cd77034b1a86e3178b318b10ae Mon Sep 17 00:00:00 2001 From: Philip Reames Date: Mon, 26 Aug 2019 20:48:35 +0000 Subject: Add a clarify comment for meaning of SafePointes [NFC] Extracted from D66688 as requested. llvm-svn: 369962 --- llvm/lib/Transforms/Vectorize/LoopVectorizationLegality.cpp | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'llvm/lib/Transforms/Vectorize/LoopVectorizationLegality.cpp') diff --git a/llvm/lib/Transforms/Vectorize/LoopVectorizationLegality.cpp b/llvm/lib/Transforms/Vectorize/LoopVectorizationLegality.cpp index 3ac1234446c..7ea842baa5e 100644 --- a/llvm/lib/Transforms/Vectorize/LoopVectorizationLegality.cpp +++ b/llvm/lib/Transforms/Vectorize/LoopVectorizationLegality.cpp @@ -924,7 +924,11 @@ bool LoopVectorizationLegality::canVectorizeWithIfConvert() { assert(TheLoop->getNumBlocks() > 1 && "Single block loops are vectorizable"); - // A list of pointers that we can safely read and write to. + // A list of pointers which are known to be dereferenceable within scope of + // the loop body for each iteration of the loop which executes. That is, + // the memory pointed to can be dereferenced (with the access size implied by + // the value's type) unconditionally within the loop header without + // introducing a new fault. SmallPtrSet SafePointes; // Collect safe addresses. -- cgit v1.2.3