diff options
Diffstat (limited to 'llvm/docs')
| -rw-r--r-- | llvm/docs/CommandGuide/llvm-nm.rst | 2 | ||||
| -rw-r--r-- | llvm/docs/GettingStarted.rst | 2 | ||||
| -rw-r--r-- | llvm/docs/GettingStartedVS.rst | 2 | ||||
| -rw-r--r-- | llvm/docs/HistoricalNotes/2003-06-25-Reoptimizer1.txt | 2 | ||||
| -rw-r--r-- | llvm/docs/YamlIO.rst | 2 |
5 files changed, 5 insertions, 5 deletions
diff --git a/llvm/docs/CommandGuide/llvm-nm.rst b/llvm/docs/CommandGuide/llvm-nm.rst index cbc7af20759..e501c4a23f4 100644 --- a/llvm/docs/CommandGuide/llvm-nm.rst +++ b/llvm/docs/CommandGuide/llvm-nm.rst @@ -79,7 +79,7 @@ D Because LLVM bitcode files typically contain objects that are not considered to have addresses until they are linked into an executable image or dynamically compiled "just-in-time", :program:`llvm-nm` does not print an address for any -symbol in a LLVM bitcode file, even symbols which are defined in the bitcode +symbol in an LLVM bitcode file, even symbols which are defined in the bitcode file. diff --git a/llvm/docs/GettingStarted.rst b/llvm/docs/GettingStarted.rst index 40dfc45b38c..1fb5211646e 100644 --- a/llvm/docs/GettingStarted.rst +++ b/llvm/docs/GettingStarted.rst @@ -1312,7 +1312,7 @@ Example with clang Clang works just like GCC by default. The standard -S and -c arguments work as usual (producing a native .s or .o file, respectively). -#. Next, compile the C file into a LLVM bitcode file: +#. Next, compile the C file into an LLVM bitcode file: .. code-block:: console diff --git a/llvm/docs/GettingStartedVS.rst b/llvm/docs/GettingStartedVS.rst index 9847c835b85..c46dc831eb9 100644 --- a/llvm/docs/GettingStartedVS.rst +++ b/llvm/docs/GettingStartedVS.rst @@ -164,7 +164,7 @@ An Example Using the LLVM Tool Chain return 0; } -2. Next, compile the C file into a LLVM bitcode file: +2. Next, compile the C file into an LLVM bitcode file: .. code-block:: bat diff --git a/llvm/docs/HistoricalNotes/2003-06-25-Reoptimizer1.txt b/llvm/docs/HistoricalNotes/2003-06-25-Reoptimizer1.txt index a7457846395..521526fbff8 100644 --- a/llvm/docs/HistoricalNotes/2003-06-25-Reoptimizer1.txt +++ b/llvm/docs/HistoricalNotes/2003-06-25-Reoptimizer1.txt @@ -132,6 +132,6 @@ is supposed to be cache-line-aligned, but it is not page-aligned. We generate instrumentation traces and optimized traces into separate trace caches. We keep the instrumented code around because you don't want to delete a trace when you still might have to return to it -(i.e., return from a llvm_first_trigger() or countPath() call.) +(i.e., return from an llvm_first_trigger() or countPath() call.) diff --git a/llvm/docs/YamlIO.rst b/llvm/docs/YamlIO.rst index a5cb637dd7e..8e7afba51dc 100644 --- a/llvm/docs/YamlIO.rst +++ b/llvm/docs/YamlIO.rst @@ -408,7 +408,7 @@ some time format (e.g. 4-May-2012 10:30pm). YAML I/O has a way to support custom formatting and parsing of scalar types by specializing ScalarTraits<> on your data type. When writing, YAML I/O will provide the native type and your specialization must create a temporary llvm::StringRef. When reading, -YAML I/O will provide a llvm::StringRef of scalar and your specialization +YAML I/O will provide an llvm::StringRef of scalar and your specialization must convert that to your native data type. An outline of a custom scalar type looks like: |
