[llvm] r367445 - [docs][FIX] Add missing word to documentation in terms of SCCs

[Philip Reames via llvm-commits]

Eek, I should have read your suggested wording more carefully. Glad you 
noticed, thanks for the fix!

Philip

On 7/31/19 9:48 AM, Johannes Doerfert via llvm-commits wrote:
> Author: jdoerfert
> Date: Wed Jul 31 09:48:42 2019
> New Revision: 367445
>
> URL: http://llvm.org/viewvc/llvm-project?rev=367445&view=rev
> Log:
> [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.
>
> Modified:
>      llvm/trunk/docs/LoopTerminology.rst
>
> Modified: llvm/trunk/docs/LoopTerminology.rst
> URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/LoopTerminology.rst?rev=367445&r1=367444&r2=367445&view=diff
> ==============================================================================
> --- llvm/trunk/docs/LoopTerminology.rst (original)
> +++ llvm/trunk/docs/LoopTerminology.rst Wed Jul 31 09:48:42 2019
> @@ -12,7 +12,7 @@ Loops are a core concept in any optimize
>   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
>
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits