Skip to content

Fix typo and grammar in docs/DebuggingTheCompiler.rst #130

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 4, 2015
Merged

Fix typo and grammar in docs/DebuggingTheCompiler.rst #130

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/DebuggingTheCompiler.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Here is how to dump the IR after the main phases of the swift compiler
get what you want to see.

#. **Performance SIL passes**. To print the SIL after the complete SIL
oprimization pipeline::
optimization pipeline::

swiftc -emit-sil -O file-swift

Expand Down Expand Up @@ -63,7 +63,7 @@ Debugging on SIL Level
Options for Dumping the SIL
```````````````````````````

Often it is not sufficient to dump the SIL at the begin or end of the
Often it is not sufficient to dump the SIL at the beginning or end of the
optimization pipeline.
The SILPassManager supports useful options to dump the SIL also between
pass runs.
Expand Down Expand Up @@ -235,7 +235,7 @@ Then by running ``lldb test -s test.lldb``, lldb will:
the function that the function pointer was passed to.

Using LLDB scripts can enable one to use complex debugger workflows without
needing to retype the various commands perfectly everytime.
needing to retype the various commands perfectly every time.

Debugging Swift Executables
---------------------------
Expand Down