[PATCH] D26675: [LoopUnroll] Modify a comment to clarify the usage of TripCount. NFC.

[Haicheng Wu via llvm-commits]

haicheng created this revision.
haicheng added reviewers: mzolotukhin, evstupac.
haicheng added a subscriber: llvm-commits.
haicheng set the repository for this revision to rL LLVM.
Herald added a subscriber: mcrosier.

Per the request of Evgeny, I add a few sentences in the comments to clarif when TripCount contains the upper bound value.


Repository:
  rL LLVM

https://reviews.llvm.org/D26675

Files:
  lib/Transforms/Utils/LoopUnroll.cpp


Index: lib/Transforms/Utils/LoopUnroll.cpp
===================================================================
--- lib/Transforms/Utils/LoopUnroll.cpp
+++ lib/Transforms/Utils/LoopUnroll.cpp
@@ -185,7 +185,9 @@
 /// terminates LatchBlock in order to remove unnecesssary instances of the
 /// test. In other words, control may exit the loop prior to TripCount
 /// iterations via an early branch, but control may not exit the loop from the
-/// LatchBlock's terminator prior to TripCount iterations.
+/// LatchBlock's terminator prior to TripCount iterations.  Parameter TripCount
+/// may contain the exact number or the upper bound.  Which one is used is 
+/// determined by the Parameter PreserveCondBr (see below).
 ///
 /// PreserveCondBr indicates whether the conditional branch of the LatchBlock
 /// needs to be preserved.  It is needed when we use trip count upper bound to


-------------- next part --------------
A non-text attachment was scrubbed...
Name: D26675.78003.patch
Type: text/x-patch
Size: 882 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20161115/71b767d8/attachment.bin>