From: Johannes Doerfert Date: Wed, 31 Jul 2019 16:48:42 +0000 (+0000) Subject: [docs][FIX] Add missing word to documentation in terms of SCCs X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=26a432079065dbfb5625c5f913ecdf3410bba094;p=llvm [docs][FIX] Add missing word to documentation in terms of SCCs In the approval of D65299, commited as rL367440, I mentioned that my proposed wording was lacking the word "maximal". It is added now for correctness. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@367445 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/LoopTerminology.rst b/docs/LoopTerminology.rst index 9229a24820e..7306167de65 100644 --- a/docs/LoopTerminology.rst +++ b/docs/LoopTerminology.rst @@ -12,7 +12,7 @@ Loops are a core concept in any optimizer. This page spells out some of the common terminology used within LLVM code to describe loop structures. -First, let's start with the basics. In LLVM, a Loop is a set of basic +First, let's start with the basics. In LLVM, a Loop is a maximal set of basic blocks that form a strongly connected component (SCC) in the Control Flow Graph (CFG) where there exists a dedicated entry/header block that dominates all other blocks within the loop. Thus, without leaving the