RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2024-12-14 23:48:56 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Further typo fixes in kaleidoscope tutorial.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@263697 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Wilfred Hughes 2016-03-17 09:26:45 +00:00
parent a66f9eb55e
commit c2e48fb33a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/tutorial/LangImpl7.rst
View File

@ -258,7 +258,7 @@ mutable variables now!
Mutable Variables in Kaleidoscope
=================================
Now that we know the sort of problem we want to tackle, lets see what
Now that we know the sort of problem we want to tackle, let's see what
this looks like in the context of our little Kaleidoscope language.
We're going to add two features:
@ -306,7 +306,7 @@ Adjusting Existing Variables for Mutation
The symbol table in Kaleidoscope is managed at code generation time by
the '``NamedValues``' map. This map currently keeps track of the LLVM
"Value\*" that holds the double value for the named variable. In order
to support mutation, we need to change this slightly, so that it
to support mutation, we need to change this slightly, so that
``NamedValues`` holds the *memory location* of the variable in question.
Note that this change is a refactoring: it changes the structure of the
code, but does not (by itself) change the behavior of the compiler. All
@ -632,7 +632,7 @@ When run, this example prints "123" and then "4", showing that we did
actually mutate the value! Okay, we have now officially implemented our
goal: getting this to work requires SSA construction in the general
case. However, to be really useful, we want the ability to define our
own local variables, lets add this next!
own local variables, let's add this next!
User-defined Local Variables
============================