[llvm-branch-commits] [llvm] c1ba991 - [NFC] Fix typo

[via llvm-branch-commits]

Author: modimo
Date: 2020-12-02T22:23:57-08:00
New Revision: c1ba991e8dd69b17fd2d88be5f6cf2b23d382c6c

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

LOG: [NFC] Fix typo

Added: 
    

Modified: 
    llvm/lib/Transforms/IPO/Inliner.cpp

Removed: 
    


################################################################################
diff  --git a/llvm/lib/Transforms/IPO/Inliner.cpp b/llvm/lib/Transforms/IPO/Inliner.cpp
index 5b6afc4be5a9..ae4441b07c4c 100644
--- a/llvm/lib/Transforms/IPO/Inliner.cpp
+++ b/llvm/lib/Transforms/IPO/Inliner.cpp
@@ -711,7 +711,7 @@ PreservedAnalyses InlinerPass::run(LazyCallGraph::SCC &InitialC,
   //
   // Note that this particular order of processing is actually critical to
   // avoid very bad behaviors. Consider *highly connected* call graphs where
-  // each function contains a small amonut of code and a couple of calls to
+  // each function contains a small amount of code and a couple of calls to
   // other functions. Because the LLVM inliner is fundamentally a bottom-up
   // inliner, it can handle gracefully the fact that these all appear to be
   // reasonable inlining candidates as it will flatten things until they become