diff options
Diffstat (limited to 'llvm/docs')
| -rw-r--r-- | llvm/docs/CoverageMappingFormat.rst | 2 | ||||
| -rw-r--r-- | llvm/docs/HowToReleaseLLVM.rst | 2 | ||||
| -rw-r--r-- | llvm/docs/LangRef.rst | 6 | ||||
| -rw-r--r-- | llvm/docs/MergeFunctions.rst | 2 | ||||
| -rw-r--r-- | llvm/docs/NVPTXUsage.rst | 2 | ||||
| -rw-r--r-- | llvm/docs/ProgrammersManual.rst | 4 | ||||
| -rw-r--r-- | llvm/docs/Statepoints.rst | 2 | ||||
| -rw-r--r-- | llvm/docs/tutorial/OCamlLangImpl1.rst | 2 |
8 files changed, 11 insertions, 11 deletions
diff --git a/llvm/docs/CoverageMappingFormat.rst b/llvm/docs/CoverageMappingFormat.rst index 47d84e37619..5e1b192898b 100644 --- a/llvm/docs/CoverageMappingFormat.rst +++ b/llvm/docs/CoverageMappingFormat.rst @@ -430,7 +430,7 @@ and can appear after ``:`` in the ``[foo : type]`` description. LEB128 ^^^^^^ -LEB128 is an unsigned interger value that is encoded using DWARF's LEB128 +LEB128 is an unsigned integer value that is encoded using DWARF's LEB128 encoding, optimizing for the case where values are small (1 byte for values less than 128). diff --git a/llvm/docs/HowToReleaseLLVM.rst b/llvm/docs/HowToReleaseLLVM.rst index f42acb7e9d2..d44ea04a9fa 100644 --- a/llvm/docs/HowToReleaseLLVM.rst +++ b/llvm/docs/HowToReleaseLLVM.rst @@ -332,7 +332,7 @@ Below are the rules regarding patching the release branch: #. During the remaining rounds of testing, only patches that fix critical regressions may be applied. -#. For dot releases all patches must mantain both API and ABI compatibility with +#. For dot releases all patches must maintain both API and ABI compatibility with the previous major release. Only bugfixes will be accepted. Merging Patches diff --git a/llvm/docs/LangRef.rst b/llvm/docs/LangRef.rst index de07c34b1bd..2073304f67e 100644 --- a/llvm/docs/LangRef.rst +++ b/llvm/docs/LangRef.rst @@ -1517,7 +1517,7 @@ operand bundle to not miscompile programs containing it. ways before control is transferred to the callee or invokee. - Calls and invokes with operand bundles have unknown read / write effect on the heap on entry and exit (even if the call target is - ``readnone`` or ``readonly``), unless they're overriden with + ``readnone`` or ``readonly``), unless they're overridden with callsite specific attributes. - An operand bundle at a call site cannot change the implementation of the called function. Inter-procedural optimizations work as @@ -3137,7 +3137,7 @@ the same register to an output and an input. If this is not safe (e.g. if the assembly contains two instructions, where the first writes to one output, and the second reads an input and writes to a second output), then the "``&``" modifier must be used (e.g. "``=&r``") to specify that the output is an -"early-clobber" output. Marking an ouput as "early-clobber" ensures that LLVM +"early-clobber" output. Marking an output as "early-clobber" ensures that LLVM will not use the same register for any inputs (other than an input tied to this output). @@ -11504,7 +11504,7 @@ The '``llvm.masked.scatter``' intrinsics is designed for writing selected vector :: - ;; This instruction unconditionaly stores data vector in multiple addresses + ;; This instruction unconditionally stores data vector in multiple addresses call @llvm.masked.scatter.v8i32 (<8 x i32> %value, <8 x i32*> %ptrs, i32 4, <8 x i1> <true, true, .. true>) ;; It is equivalent to a list of scalar stores diff --git a/llvm/docs/MergeFunctions.rst b/llvm/docs/MergeFunctions.rst index b2f6030edc1..377ea4d698d 100644 --- a/llvm/docs/MergeFunctions.rst +++ b/llvm/docs/MergeFunctions.rst @@ -697,7 +697,7 @@ Below is detailed body description. If “F” may be overridden ------------------------ As follows from ``mayBeOverridden`` comments: “whether the definition of this -global may be replaced by something non-equivalent at link time”. If so, thats +global may be replaced by something non-equivalent at link time”. If so, that's ok: we can use alias to *F* instead of *G* or change call instructions itself. HasGlobalAliases, removeUsers diff --git a/llvm/docs/NVPTXUsage.rst b/llvm/docs/NVPTXUsage.rst index fc697ca0046..71acb0c79fc 100644 --- a/llvm/docs/NVPTXUsage.rst +++ b/llvm/docs/NVPTXUsage.rst @@ -395,7 +395,7 @@ JIT compiling a PTX string to a device binary: .. code-block:: c++ CUmodule module; - CUfunction funcion; + CUfunction function; // JIT compile a null-terminated PTX string cuModuleLoadData(&module, (void*)PTXString); diff --git a/llvm/docs/ProgrammersManual.rst b/llvm/docs/ProgrammersManual.rst index 665e30aeb67..fa2b37a8793 100644 --- a/llvm/docs/ProgrammersManual.rst +++ b/llvm/docs/ProgrammersManual.rst @@ -420,7 +420,7 @@ system in place to ensure that names do not conflict. If two different modules use the same string, they will all be turned on when the name is specified. This allows, for example, all debug information for instruction scheduling to be enabled with ``-debug-only=InstrSched``, even if the source lives in multiple -files. The name must not include a comma (,) as that is used to seperate the +files. The name must not include a comma (,) as that is used to separate the arguments of the ``-debug-only`` option. For performance reasons, -debug-only is not available in optimized build @@ -1135,7 +1135,7 @@ llvm/ADT/StringSet.h ``StringSet`` is a thin wrapper around :ref:`StringMap\<char\> <dss_stringmap>`, and it allows efficient storage and retrieval of unique strings. -Functionally analogous to ``SmallSet<StringRef>``, ``StringSet`` also suports +Functionally analogous to ``SmallSet<StringRef>``, ``StringSet`` also supports iteration. (The iterator dereferences to a ``StringMapEntry<char>``, so you need to call ``i->getKey()`` to access the item of the StringSet.) On the other hand, ``StringSet`` doesn't support range-insertion and diff --git a/llvm/docs/Statepoints.rst b/llvm/docs/Statepoints.rst index b0e4f813179..1e46152443e 100644 --- a/llvm/docs/Statepoints.rst +++ b/llvm/docs/Statepoints.rst @@ -262,7 +262,7 @@ As a practical consideration, many garbage-collected systems allow code that is collector-aware ("managed code") to call code that is not collector-aware ("unmanaged code"). It is common that such calls must also be safepoints, since it is desirable to allow the collector to run during the execution of -unmanaged code. Futhermore, it is common that coordinating the transition from +unmanaged code. Furthermore, it is common that coordinating the transition from managed to unmanaged code requires extra code generation at the call site to inform the collector of the transition. In order to support these needs, a statepoint may be marked as a GC transition, and data that is necessary to diff --git a/llvm/docs/tutorial/OCamlLangImpl1.rst b/llvm/docs/tutorial/OCamlLangImpl1.rst index cf968b5ae89..9de92305a1c 100644 --- a/llvm/docs/tutorial/OCamlLangImpl1.rst +++ b/llvm/docs/tutorial/OCamlLangImpl1.rst @@ -106,7 +106,7 @@ support the if/then/else construct, a for loop, user defined operators, JIT compilation with a simple command line interface, etc. Because we want to keep things simple, the only datatype in Kaleidoscope -is a 64-bit floating point type (aka 'float' in O'Caml parlance). As +is a 64-bit floating point type (aka 'float' in OCaml parlance). As such, all values are implicitly double precision and the language doesn't require type declarations. This gives the language a very nice and simple syntax. For example, the following simple example computes |
