24
24
// / is highly bug prone and infeasible.
25
25
// /
26
26
// / 3. Fixup OSSA after deletion so SIL remains valid. Allowing OSSA to be
27
- // / invalid across API boundaries creates an intractible problem and makes it
27
+ // / invalid across API boundaries creates an intractable problem and makes it
28
28
// / impossible to design composable OSSA utilities.
29
29
// /
30
30
// / Strategies for SIL transformation:
53
53
// / instruction iterators during deletion. This is because deleting a single
54
54
// / instruction may require deleting other instructions, such as debug info and
55
55
// / scope-ending instructions. In OSSA code, deleting an instruction may even
56
- // / cause new instructions to be inserted. This is best handled by aquiring an
56
+ // / cause new instructions to be inserted. This is best handled by acquiring an
57
57
// / UpdatingInstructionIterator from the InstructionDeleter. This is usually
58
58
// / done via InstructionDeleter::updatingRange(SILBasicBlock *).
59
59
// / InstructionDeleter::getIteratorRegistry().makeIterator() offers more
64
64
// / For data structures that contain instruction pointers and persist across
65
65
// / calls to forceDelete* or cleanupDeadInstructions... There is no need to
66
66
// / create an updating iterator. Simply check Instruction::isDeleted() when
67
- // / retriving a pointer from the data structure.
67
+ // / retrieving a pointer from the data structure.
68
68
// /
69
69
// / Using InstModCallbacks:
70
70
// /
@@ -192,7 +192,7 @@ class InstructionDeleter {
192
192
// / lifetimes of the operands of \c inst once it is deleted. This function
193
193
// / will not clean up dead code resulting from the instruction's removal. To
194
194
// / do so, invoke the method \c cleanupDeadCode of this instance, once the SIL
195
- // / of the contaning function is made consistent.
195
+ // / of the containing function is made consistent.
196
196
// /
197
197
// / \pre the instruction to be deleted must not have any use other than
198
198
// / incidental uses.
@@ -213,7 +213,7 @@ class InstructionDeleter {
213
213
// / Clean up dead instructions that are tracked by this instance and all
214
214
// / instructions that transitively become dead.
215
215
// /
216
- // / \pre the function contaning dead instructions must be consistent (i.e., no
216
+ // / \pre the function containing dead instructions must be consistent (i.e., no
217
217
// / under or over releases). Note that if \c forceDelete call leaves the
218
218
// / function body in an inconsistent state, it needs to be made consistent
219
219
// / before this method is invoked.
0 commit comments