aboutsummaryrefslogtreecommitdiffstats
path: root/test/Transforms/ObjCARC/allocas.ll
diff options
context:
space:
mode:
Diffstat (limited to 'test/Transforms/ObjCARC/allocas.ll')
-rw-r--r--test/Transforms/ObjCARC/allocas.ll4
1 files changed, 2 insertions, 2 deletions
diff --git a/test/Transforms/ObjCARC/allocas.ll b/test/Transforms/ObjCARC/allocas.ll
index 5065673..7347a8f 100644
--- a/test/Transforms/ObjCARC/allocas.ll
+++ b/test/Transforms/ObjCARC/allocas.ll
@@ -28,7 +28,7 @@ declare void @llvm.dbg.value(metadata, i64, metadata)
declare i8* @objc_msgSend(i8*, i8*, ...)
-; In the presense of allocas, unconditionally remove retain/release pairs only
+; In the presence of allocas, unconditionally remove retain/release pairs only
; if they are known safe in both directions. This prevents matching up an inner
; retain with the boundary guarding release in the following situation:
;
@@ -336,7 +336,7 @@ bb3:
ret void
}
-; Make sure in the presense of allocas, if we find a cfghazard we do not perform
+; Make sure in the presence of allocas, if we find a cfghazard we do not perform
; code motion even if we are known safe. These two concepts are separate and
; should be treated as such.
;