Author: sylvestre Date: Tue Jan 1 04:51:14 2019 New Revision: 350192 URL: http://llvm.org/viewvc/llvm-project?rev=350192&view=rev Log: Fix some typos in the clang doc. Fixed with: $ codespell -w ClangFormatStyleOptions.rst Toolchain.rst LanguageExtensions.rst ClangCommandLineReference.rst
Modified: cfe/trunk/docs/ClangCommandLineReference.rst cfe/trunk/docs/ClangFormatStyleOptions.rst cfe/trunk/docs/LanguageExtensions.rst cfe/trunk/docs/Toolchain.rst Modified: cfe/trunk/docs/ClangCommandLineReference.rst URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/ClangCommandLineReference.rst?rev=350192&r1=350191&r2=350192&view=diff ============================================================================== --- cfe/trunk/docs/ClangCommandLineReference.rst (original) +++ cfe/trunk/docs/ClangCommandLineReference.rst Tue Jan 1 04:51:14 2019 @@ -158,7 +158,7 @@ Compile CUDA code for host only. Has no .. option:: --cuda-include-ptx=<arg>, --no-cuda-include-ptx=<arg> -Include PTX for the follwing GPU architecture (e.g. sm\_35) or 'all'. May be specified more than once. +Include PTX for the following GPU architecture (e.g. sm\_35) or 'all'. May be specified more than once. .. option:: --cuda-noopt-device-debug, --no-cuda-noopt-device-debug Modified: cfe/trunk/docs/ClangFormatStyleOptions.rst URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/ClangFormatStyleOptions.rst?rev=350192&r1=350191&r2=350192&view=diff ============================================================================== --- cfe/trunk/docs/ClangFormatStyleOptions.rst (original) +++ cfe/trunk/docs/ClangFormatStyleOptions.rst Tue Jan 1 04:51:14 2019 @@ -1398,7 +1398,7 @@ the configuration (without a prefix: ``A **JavaImportGroups** (``std::vector<std::string>``) A vector of prefixes ordered by the desired groups for Java imports. - Each group is seperated by a newline. Static imports will also follow the + Each group is separated by a newline. Static imports will also follow the same grouping convention above all non-static imports. One group's prefix can be a subset of another - the longest prefix is always matched. Within a group, the imports are ordered lexicographically. Modified: cfe/trunk/docs/LanguageExtensions.rst URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/LanguageExtensions.rst?rev=350192&r1=350191&r2=350192&view=diff ============================================================================== --- cfe/trunk/docs/LanguageExtensions.rst (original) +++ cfe/trunk/docs/LanguageExtensions.rst Tue Jan 1 04:51:14 2019 @@ -2725,7 +2725,7 @@ same namespace. For instance: Without the namespaces on the macros, ``other_function`` will be annotated with ``[[noreturn]]`` instead of ``__attribute__((unavailable))``. This may seem like a contrived example, but its very possible for this kind of situation to appear -in real code if the pragmas are spread out accross a large file. +in real code if the pragmas are spread out across a large file. Subject Match Rules ------------------- Modified: cfe/trunk/docs/Toolchain.rst URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/Toolchain.rst?rev=350192&r1=350191&r2=350192&view=diff ============================================================================== --- cfe/trunk/docs/Toolchain.rst (original) +++ cfe/trunk/docs/Toolchain.rst Tue Jan 1 04:51:14 2019 @@ -100,14 +100,14 @@ currently-supported languages are: In each case, GCC will be invoked to compile the input. -Assember --------- +Assembler +--------- Clang can either use LLVM's integrated assembler or an external system-specific tool (for instance, the GNU Assembler on GNU OSes) to produce machine code from assembly. By default, Clang uses LLVM's integrated assembler on all targets where it is -supported. If you wish to use the system assember instead, use the +supported. If you wish to use the system assembler instead, use the ``-fno-integrated-as`` option. Linker _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits