[llvm-project] Fix typo "propogate" (#114795)

Author: jayfoad

clang/test/Analysis/malloc.c

@@ -1829,7 +1829,7 @@ void testConstEscapeThroughAnotherField(void) {
 } // no-warning
 
 // PR15623
-int testNoCheckerDataPropogationFromLogicalOpOperandToOpResult(void) {
+int testNoCheckerDataPropagationFromLogicalOpOperandToOpResult(void) {
    char *param = malloc(10);
    char *value = malloc(10);
    int ok = (param && value);

lld/test/Unit/lit.cfg.py

@@ -38,7 +38,7 @@
     config.environment["PATH"] = os.path.pathsep.join((
             config.shlibdir, config.environment["PATH"]))
 
-# Win32 may use %SYSTEMDRIVE% during file system shell operations, so propogate.
+# Win32 may use %SYSTEMDRIVE% during file system shell operations, so propagate.
 if sys.platform == "win32" and "SYSTEMDRIVE" in os.environ:
     config.environment["SYSTEMDRIVE"] = os.environ["SYSTEMDRIVE"]
 

llvm/docs/HistoricalNotes/2001-05-18-ExceptionHandling.txt

@@ -70,7 +70,7 @@ void TestFunction(...) {
     // execution continues after the try block: the exception is consumed
   } catch (double) {
     ...double stuff...
-   throw;            // Exception is propogated
+   throw;            // Exception is propagated
   }
 }
 
@@ -83,14 +83,14 @@ Func:
   %b = alloca B   // minor detail for this example
   B::B(%b)
 
-  call foo() with fooCleanup // An exception in foo is propogated to fooCleanup
-  call bar() with barCleanup // An exception in bar is propogated to barCleanup
+  call foo() with fooCleanup // An exception in foo is propagated to fooCleanup
+  call bar() with barCleanup // An exception in bar is propagated to barCleanup
 
   %c = alloca C
   C::C(c)
   %d = alloca D
   D::D(d)
-  call baz() with bazCleanup // An exception in baz is propogated to bazCleanup
+  call baz() with bazCleanup // An exception in baz is propagated to bazCleanup
   d->~D();
 EndTry:                   // This label corresponds to the end of the try block
   c->~C()       // These could also throw, these are also ignored

llvm/docs/HistoricalNotes/2002-05-12-InstListChange.txt

@@ -18,7 +18,7 @@ linear search of the basic block the instruction is contained in... just
 to insert an instruction before another instruction, or to delete an 
 instruction!  This complicates algorithms that should be very simple (like 
 simple constant propagation), because they aren't actually sparse anymore,
-they have to traverse basic blocks to remove constant propogated 
+they have to traverse basic blocks to remove constant propagated
 instructions.
 
 Additionally, adding or removing instructions to a basic block 

llvm/lib/Transforms/IPO/AttributorAttributes.cpp

@@ -9240,12 +9240,12 @@ struct AAValueConstantRangeReturned
     : AAReturnedFromReturnedValues<AAValueConstantRange,
                                    AAValueConstantRangeImpl,
                                    AAValueConstantRangeImpl::StateType,
-                                   /* PropogateCallBaseContext */ true> {
+                                   /* PropagateCallBaseContext */ true> {
   using Base =
       AAReturnedFromReturnedValues<AAValueConstantRange,
                                    AAValueConstantRangeImpl,
                                    AAValueConstantRangeImpl::StateType,
-                                   /* PropogateCallBaseContext */ true>;
+                                   /* PropagateCallBaseContext */ true>;
   AAValueConstantRangeReturned(const IRPosition &IRP, Attributor &A)
       : Base(IRP, A) {}
 

llvm/lib/Transforms/IPO/IROutliner.cpp

@@ -1513,7 +1513,7 @@ CallInst *replaceCalledFunction(Module &M, OutlinableRegion &Region) {
   // Transfer any debug information.
   Call->setDebugLoc(Region.Call->getDebugLoc());
   // Since our output may determine which branch we go to, we make sure to
-  // propogate this new call value through the module.
+  // propagate this new call value through the module.
   OldCall->replaceAllUsesWith(Call);
 
   // Remove the old instruction.

llvm/test/CodeGen/AArch64/i128-fast-isel-fallback.ll

@@ -6,7 +6,7 @@ define void @test1() {
   call void  @test2(i128 %1)
   ret void
 
-; The i128 is 0 so the we can test to make sure it is propogated into the x
+; The i128 is 0 so the we can test to make sure it is propagated into the x
 ; registers that make up the i128 pair
 
 ; CHECK:  mov  x0, xzr

llvm/test/CodeGen/AMDGPU/waitcnt-loop-single-basic-block.mir

@@ -1,6 +1,6 @@
 # RUN: llc -mtriple=amdgcn -mcpu=gfx900 -run-pass=si-insert-waitcnts -verify-machineinstrs %s -o - | FileCheck -check-prefix=GCN %s
 
-# Check that the waitcnt propogates info in the case of a single basic block loop
+# Check that the waitcnt propagates info in the case of a single basic block loop
 
 # GCN-LABEL: waitcnt-loop-single-basic-block
 # GCN: bb.0

llvm/test/DebugInfo/MIR/X86/livedebugvalues_basic_diamond.mir

@@ -1,7 +1,7 @@
 --- |
   ; RUN: llc %s -march=x86-64 -run-pass=livedebugvalues -o - | FileCheck %s -implicit-check-not=DBG_VALUE
 
-  ; Check that DBG_VALUE instructions are propogated through a CFG containing
+  ; Check that DBG_VALUE instructions are propagated through a CFG containing
   ; a diamond that doesn't move or clobber their locations.
 
   ; CHECK-LABEL: bb.0.entry:

llvm/test/DebugInfo/MIR/X86/livedebugvalues_basic_diamond_match_clobber.mir

@@ -1,7 +1,7 @@
 --- |
   ; RUN: llc %s -march=x86-64 -run-pass=livedebugvalues -o - | FileCheck %s -implicit-check-not=DBG_VALUE
 
-  ; Check that DBG_VALUE instructions are only propogated into the top blocks of
+  ; Check that DBG_VALUE instructions are only propagated into the top blocks of
   ; a diamond when the location is clobbered and not into the successor block.
 
   ; CHECK-LABEL: bb.0.entry: