From 0f4203861f730cf7868d7f359df0fc1247fe7fc1 Mon Sep 17 00:00:00 2001 From: Benjamin Kramer Date: Mon, 12 Oct 2009 14:46:08 +0000 Subject: Documentation: Perform automated correction of common typos. llvm-svn: 83849 --- llvm/docs/tutorial/LangImpl3.html | 4 ++-- llvm/docs/tutorial/LangImpl4.html | 2 +- llvm/docs/tutorial/OCamlLangImpl3.html | 4 ++-- llvm/docs/tutorial/OCamlLangImpl4.html | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) (limited to 'llvm/docs/tutorial') diff --git a/llvm/docs/tutorial/LangImpl3.html b/llvm/docs/tutorial/LangImpl3.html index bc5db46d905..e3d2117c4e6 100644 --- a/llvm/docs/tutorial/LangImpl3.html +++ b/llvm/docs/tutorial/LangImpl3.html @@ -183,7 +183,7 @@ Value *VariableExprAST::Codegen() {

References to variables are also quite simple using LLVM. In the simple version -of Kaleidoscope, we assume that the variable has already been emited somewhere +of Kaleidoscope, we assume that the variable has already been emitted somewhere and its value is available. In practice, the only values that can be in the NamedValues map are function arguments. This code simply checks to see that the specified name is in the map (if not, an @@ -362,7 +362,7 @@ definition of this function.

first, we want to allow 'extern'ing a function more than once, as long as the prototypes for the externs match (since all arguments have the same type, we just have to check that the number of arguments match). Second, we want to -allow 'extern'ing a function and then definining a body for it. This is useful +allow 'extern'ing a function and then defining a body for it. This is useful when defining mutually recursive functions.

In order to implement this, the code above first checks to see if there is diff --git a/llvm/docs/tutorial/LangImpl4.html b/llvm/docs/tutorial/LangImpl4.html index 8310b61a75d..3188135384e 100644 --- a/llvm/docs/tutorial/LangImpl4.html +++ b/llvm/docs/tutorial/LangImpl4.html @@ -209,7 +209,7 @@ requires a pointer to the Module (through the ModuleProvider) to construct itself. Once it is set up, we use a series of "add" calls to add a bunch of LLVM passes. The first pass is basically boilerplate, it adds a pass so that later optimizations know how the data structures in the program are -layed out. The "TheExecutionEngine" variable is related to the JIT, +laid out. The "TheExecutionEngine" variable is related to the JIT, which we will get to in the next section.

In this case, we choose to add 4 optimization passes. The passes we chose diff --git a/llvm/docs/tutorial/OCamlLangImpl3.html b/llvm/docs/tutorial/OCamlLangImpl3.html index 0ba04ab8af2..a59887522ee 100644 --- a/llvm/docs/tutorial/OCamlLangImpl3.html +++ b/llvm/docs/tutorial/OCamlLangImpl3.html @@ -159,7 +159,7 @@ uses "the foo::get(..)" idiom instead of "new foo(..)" or "foo::Create(..)".

References to variables are also quite simple using LLVM. In the simple -version of Kaleidoscope, we assume that the variable has already been emited +version of Kaleidoscope, we assume that the variable has already been emitted somewhere and its value is available. In practice, the only values that can be in the Codegen.named_values map are function arguments. This code simply checks to see that the specified name is in the map (if not, an unknown @@ -323,7 +323,7 @@ code above.

first, we want to allow 'extern'ing a function more than once, as long as the prototypes for the externs match (since all arguments have the same type, we just have to check that the number of arguments match). Second, we want to -allow 'extern'ing a function and then definining a body for it. This is useful +allow 'extern'ing a function and then defining a body for it. This is useful when defining mutually recursive functions.

diff --git a/llvm/docs/tutorial/OCamlLangImpl4.html b/llvm/docs/tutorial/OCamlLangImpl4.html index 238fc53392d..26f253249bb 100644 --- a/llvm/docs/tutorial/OCamlLangImpl4.html +++ b/llvm/docs/tutorial/OCamlLangImpl4.html @@ -224,7 +224,7 @@ requires a pointer to the the_module (through the the_module_provider) to construct itself. Once it is set up, we use a series of "add" calls to add a bunch of LLVM passes. The first pass is basically boilerplate, it adds a pass so that later optimizations know how the -data structures in the program are layed out. The +data structures in the program are laid out. The "the_execution_engine" variable is related to the JIT, which we will get to in the next section.

-- cgit v1.2.3