[llvm] c0f34c8 - [Coroutine] Fix typos in comment

[Jannik Silvanus via llvm-commits]

Author: Jannik Silvanus
Date: 2023-01-26T12:42:08+01:00
New Revision: c0f34c8ce0e51985030c8946aff5e4052a5b01e6

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

LOG: [Coroutine] Fix typos in comment

Added: 
    

Modified: 
    llvm/lib/Transforms/Coroutines/CoroFrame.cpp

Removed: 
    


################################################################################
diff  --git a/llvm/lib/Transforms/Coroutines/CoroFrame.cpp b/llvm/lib/Transforms/Coroutines/CoroFrame.cpp
index e98c601648e04..814c839cea739 100644
--- a/llvm/lib/Transforms/Coroutines/CoroFrame.cpp
+++ b/llvm/lib/Transforms/Coroutines/CoroFrame.cpp
@@ -637,10 +637,10 @@ void FrameTypeBuilder::addFieldForAllocas(const Function &F,
     return;
   }
 
-  // Because there are pathes from the lifetime.start to coro.end
+  // Because there are paths from the lifetime.start to coro.end
   // for each alloca, the liferanges for every alloca is overlaped
   // in the blocks who contain coro.end and the successor blocks.
-  // So we choose to skip there blocks when we calculates the liferange
+  // So we choose to skip there blocks when we calculate the liferange
   // for each alloca. It should be reasonable since there shouldn't be uses
   // in these blocks and the coroutine frame shouldn't be used outside the
   // coroutine body.