From: Stefanos Baziotis Date: Wed, 23 Sep 2020 19:53:05 +0000 (+0300) Subject: [LoopTerminology][NFC] Fix formatting typo X-Git-Tag: llvmorg-13-init~11121 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=7aa982a57ce0dbf8fdbd276004615ddcf729c906;p=platform%2Fupstream%2Fllvm.git [LoopTerminology][NFC] Fix formatting typo --- diff --git a/llvm/docs/LoopTerminology.rst b/llvm/docs/LoopTerminology.rst index fc46198..0870ab9 100644 --- a/llvm/docs/LoopTerminology.rst +++ b/llvm/docs/LoopTerminology.rst @@ -291,7 +291,7 @@ In general, it's easier to use SCEV in loops that are in LCSSA form. The evolution of a scalar (loop-variant) expression that SCEV can analyze is, by definition, relative to a loop. An expression is represented in LLVM by an -`llvm::Instruction `. +`llvm::Instruction `_. If the expression is inside two (or more) loops (which can only happen if the loops are nested, like in the example above) and you want to get an analysis of its evolution (from SCEV),