[llvm] 1f83726 - [Coroutines] Fix a typo in documentation

[Xun Li via llvm-commits]

Author: Xun Li
Date: 2020-09-14T18:56:57-07:00
New Revision: 1f837265eb082441337a42420bf415a99c3f4baa

URL: https://github.com/llvm/llvm-project/commit/1f837265eb082441337a42420bf415a99c3f4baa
DIFF: https://github.com/llvm/llvm-project/commit/1f837265eb082441337a42420bf415a99c3f4baa.diff

LOG: [Coroutines] Fix a typo in documentation

In the example, the variable that's crossing suspend point was referred wrongly, fix it.

Differential Revision: https://reviews.llvm.org/D83563

Added: 
    

Modified: 
    llvm/docs/Coroutines.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/Coroutines.rst b/llvm/docs/Coroutines.rst
index 3f7cddef9b37..5afb33fa0a0a 100644
--- a/llvm/docs/Coroutines.rst
+++ b/llvm/docs/Coroutines.rst
@@ -257,10 +257,10 @@ Coroutine Transformation
 One of the steps of coroutine lowering is building the coroutine frame. The
 def-use chains are analyzed to determine which objects need be kept alive across
 suspend points. In the coroutine shown in the previous section, use of virtual register 
-`%n.val` is separated from the definition by a suspend point, therefore, it 
+`%inc` is separated from the definition by a suspend point, therefore, it 
 cannot reside on the stack frame since the latter goes away once the coroutine 
 is suspended and control is returned back to the caller. An i32 slot is 
-allocated in the coroutine frame and `%n.val` is spilled and reloaded from that
+allocated in the coroutine frame and `%inc` is spilled and reloaded from that
 slot as needed.
 
 We also store addresses of the resume and destroy functions so that the