[PATCH] D109029: [SCEV] Clarify requirements for zero-stride to be UB
Philip Reames via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Wed Sep 1 14:01:30 PDT 2021
This revision was automatically updated to reflect the committed changes.
Closed by commit rG73b951a7f7dc: [SCEV] Clarify requirements for zero-stride to be UB (authored by reames).
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D109029/new/
https://reviews.llvm.org/D109029
Files:
llvm/lib/Analysis/ScalarEvolution.cpp
Index: llvm/lib/Analysis/ScalarEvolution.cpp
===================================================================
--- llvm/lib/Analysis/ScalarEvolution.cpp
+++ llvm/lib/Analysis/ScalarEvolution.cpp
@@ -11633,13 +11633,15 @@
// a) IV is either nuw or nsw depending upon signedness (indicated by the
// NoWrap flag).
// b) loop is single exit with no side effects.
+ // c) loop has no abnormal exits
//
//
// Precondition a) implies that if the stride is negative, this is a single
// trip loop. The backedge taken count formula reduces to zero in this case.
//
- // Precondition b) implies that if rhs is invariant in L, then unknown
- // stride being zero means the backedge can't be taken without UB.
+ // Precondition b) and c) combine to imply that if rhs is invariant in L,
+ // then a zero stride means the backedge can't be taken without executing
+ // undefined behavior.
//
// The positive stride case is the same as isKnownPositive(Stride) returning
// true (original behavior of the function).
@@ -11657,7 +11659,7 @@
// A[i] = i;
//
if (PredicatedIV || !NoWrap || isKnownNonPositive(Stride) ||
- !loopIsFiniteByAssumption(L))
+ !loopIsFiniteByAssumption(L) || !loopHasNoAbnormalExits(L))
return getCouldNotCompute();
if (!isKnownNonZero(Stride)) {
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D109029.370052.patch
Type: text/x-patch
Size: 1379 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20210901/d37c0ed9/attachment.bin>
More information about the llvm-commits
mailing list