https://gcc.gnu.org/g:7fbc286a1ddfc1eed5b5682c4bf808ef3e0007f2
commit r17-1007-g7fbc286a1ddfc1eed5b5682c4bf808ef3e0007f2 Author: Dhruv Chawla <[email protected]> Date: Wed May 13 11:10:49 2026 +0000 doc: Fix typos in various files Signed-off-by: Dhruv Chawla <[email protected]> gcc/ChangeLog: * doc/analyzer.texi: Fix typos. * doc/cpp.texi: Likewise. * doc/extend.texi: Likewise. * doc/gcov.texi: Likewise. * doc/gm2.texi: Likewise. * doc/gty.texi: Likewise. * doc/install.texi: Likewise. * doc/invoke.texi: Likewise. * doc/libgdiagnostics/topics/compatibility.rst: Likewise. * doc/libgdiagnostics/topics/physical-locations.rst: Likewise. * doc/libgdiagnostics/tutorial/07-execution-paths.rst: Likewise. * doc/libgdiagnostics/tutorial/08-message-buffers.rst: Likewise. * doc/match-and-simplify.texi: Likewise. * doc/md.texi: Likewise. * doc/optinfo.texi: Likewise. * doc/params.texi: Likewise. * doc/poly-int.texi: Likewise. * doc/riscv-ext.texi: Likewise. * doc/rtl.texi: Likewise. * doc/sourcebuild.texi: Likewise. * doc/tm.texi: Likewise. * doc/tm.texi.in: Likewise. * doc/tree-ssa.texi: Likewise. Diff: --- gcc/doc/analyzer.texi | 4 ++-- gcc/doc/cpp.texi | 2 +- gcc/doc/extend.texi | 16 +++++++-------- gcc/doc/gcov.texi | 6 +++--- gcc/doc/gm2.texi | 6 +++--- gcc/doc/gty.texi | 2 +- gcc/doc/install.texi | 4 ++-- gcc/doc/invoke.texi | 10 ++++----- gcc/doc/libgdiagnostics/topics/compatibility.rst | 4 ++-- .../libgdiagnostics/topics/physical-locations.rst | 2 +- .../tutorial/07-execution-paths.rst | 2 +- .../tutorial/08-message-buffers.rst | 2 +- gcc/doc/match-and-simplify.texi | 2 +- gcc/doc/md.texi | 24 +++++++++++----------- gcc/doc/optinfo.texi | 2 +- gcc/doc/params.texi | 2 +- gcc/doc/poly-int.texi | 6 +++--- gcc/doc/riscv-ext.texi | 2 +- gcc/doc/rtl.texi | 4 ++-- gcc/doc/sourcebuild.texi | 2 +- gcc/doc/tm.texi | 22 ++++++++++---------- gcc/doc/tm.texi.in | 4 ++-- gcc/doc/tree-ssa.texi | 2 +- 23 files changed, 66 insertions(+), 66 deletions(-) diff --git a/gcc/doc/analyzer.texi b/gcc/doc/analyzer.texi index d530ea497a5d..05ae4ae39554 100644 --- a/gcc/doc/analyzer.texi +++ b/gcc/doc/analyzer.texi @@ -875,8 +875,8 @@ This will dump a @file{SRC.eg.txt} file containing the full @code{exploded_graph}. I use @code{diff -u50 -p} to compare two different such files (e.g. before and after a patch) to find the first place where the two graphs diverge. The option @option{-fdump-noaddr} will suppress -printing pointers withihn the dumps (which would otherwise hide the real -differences with irrelevent churn). +printing pointers within the dumps (which would otherwise hide the real +differences with irrelevant churn). The option @option{-fdump-analyzer-json} will dump both the supergraph and the exploded graph in compressed JSON form. diff --git a/gcc/doc/cpp.texi b/gcc/doc/cpp.texi index ca328b443aed..69a74617a0fc 100644 --- a/gcc/doc/cpp.texi +++ b/gcc/doc/cpp.texi @@ -590,7 +590,7 @@ reject source code containing ``other'' tokens. In ASCII, the only ``other'' characters are @samp{@@}, @samp{$}, @samp{`}, and control characters other than NUL (all bits zero). (Note that @samp{$} is normally considered a letter.) All bytes with the high bit set -(numeric range 0x7F--0xFF) that were not succesfully interpreted as +(numeric range 0x7F--0xFF) that were not successfully interpreted as part of an extended character in the input encoding are also ``other'' in the present implementation. diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index d9a6594d72a1..f4d92467826a 100644 --- a/gcc/doc/extend.texi +++ b/gcc/doc/extend.texi @@ -1740,7 +1740,7 @@ extern void f3 [[gnu::section ("bar")]] (void); @end smallexample Typedefs follow the same attribute placement rules for other as other -declarations. These declarations are all valid with similiar meanings. +declarations. These declarations are all valid with similar meanings. @smallexample [[gnu::unavailable]] typedef int *t1; @@ -1886,7 +1886,7 @@ to the function is accessed according to @var{access-mode}, which must be one of @code{read_only}, @code{read_write}, @code{write_only}, or @code{none}. The semantics of these modes are described below. -The argument the attribute applies to is identifed by @var{ref-index}, which +The argument the attribute applies to is identified by @var{ref-index}, which is an integer constant representing its position in the argument list. Argument numbering starts from 1. You can specify multiple @code{access} attributes to describe the access modes of different arguments, but multiple @@ -2585,7 +2585,7 @@ member or a pointer field of a structure. It indicates that the number of the elements of the array that is held by the flexible array member field, or is pointed to by the pointer field, is given by the field -named by the identifer @var{count} in the same structure as the +named by the identifier @var{count} in the same structure as the flexible array member or the pointer field. This attribute is available only in C for now. @@ -7741,7 +7741,7 @@ This attribute applies to functions. It tells GCC to keep interrupts masked for the whole function. Without this attribute, -GCC tries to reenable interrupts for as much of the function as it can. +GCC tries to re-enable interrupts for as much of the function as it can. @atindex @code{use_debug_exception_return}, MIPS @item use_debug_exception_return @@ -8358,7 +8358,7 @@ per-function basis. @item arch= Specifies the architecture version and architectural extensions to use for this function. The behavior and permissible arguments are the same as -for the @option{-march=} command-line option, in addtion, it also support +for the @option{-march=} command-line option, in addition, it also support extension enablement list, a list of extension name and prefixed with @code{+}, like @code{arch=+zba} means enable @code{zba} extension. Multiple extension can be enabled by separating them with a comma. For example: @@ -16373,7 +16373,7 @@ i.e.@: they subtract 2 unsigned values from the first unsigned value, set what the last argument points to to 1 if any of the two subtractions overflowed (otherwise 0) and return the result of the subtractions. Note, while all the first 3 arguments can have arbitrary values, better code -will be emitted if one of them (preferrably the third one) has only values +will be emitted if one of them (preferably the third one) has only values 0 or 1 (i.e.@: carry-in). @enddefbuiltin @@ -17790,7 +17790,7 @@ void foo () @{ delete a; // This pair of allocation/deallocation operators can be omitted // or replaced with int _temp; int *a = &_temp; etc.@: void *b = ::operator new (32); - ::operator delete (b); // This one cannnot. + ::operator delete (b); // This one cannot. void *c = __builtin_operator_new (32); __builtin_operator_delete (c); // This one can. @} @@ -26054,7 +26054,7 @@ unsigned int); Extract an element from two concatenated vectors starting at the given byte index. The index is based on big endian order for a little endian system. Similarly, the index is based on little endian order for a big endian system. -The extraced elements are zero-extended and put in doubleword 1 +The extracted elements are zero-extended and put in doubleword 1 according to natural element order. If the byte index is out of range for the data type, the intrinsic will be rejected. For little-endian, this output will match the placement by the hardware instruction (vextdubvrx, vextduhvrx, diff --git a/gcc/doc/gcov.texi b/gcc/doc/gcov.texi index 7080f7c4a2a4..52239d2437ae 100644 --- a/gcc/doc/gcov.texi +++ b/gcc/doc/gcov.texi @@ -227,7 +227,7 @@ path 4 not covered: lines 8 8(false) 11(true) 11 13(false) 16 17 @end smallexample This means to cover path 2 you must run lines 8, 11, 13, 14, and 17, -evaluting the decision at 8 false and the decisions at 11 and 13 to +evaluating the decision at 8 false and the decisions at 11 and 13 to @code{false}. @item --prime-paths-source [=@var{type}] @@ -625,7 +625,7 @@ and exit without doing any further processing. @item -w @itemx --verbose -Print verbose informations related to basic blocks and arcs. +Print verbose information related to basic blocks and arcs. @item -x @itemx --hash-filenames @@ -1248,7 +1248,7 @@ extended regular expressions (like @command{grep -E}), so the pattern match too. @option{--include} and @option{--exclude} can be used multiple times, and if a name matches multiple filters it is the last one to match which takes preference. For example, to match -@code{main} and the @code{int} instatiation of @code{inc}, while +@code{main} and the @code{int} instantiation of @code{inc}, while omitting the @code{Foo} constructor: @smallexample diff --git a/gcc/doc/gm2.texi b/gcc/doc/gm2.texi index 4e2721bd1cb8..2991b2b05d15 100644 --- a/gcc/doc/gm2.texi +++ b/gcc/doc/gm2.texi @@ -2122,7 +2122,7 @@ EXCEPT (* Now fixup. Determine the source of the exception and retry. *) IF head = NIL THEN - printf ("list was empty, add sentinal\n"); + printf ("list was empty, add sentinel\n"); Add (head, -1) ; RETRY (* Jump back to the begin statement. *) ELSIF p^.next = NIL @@ -2159,7 +2159,7 @@ END lazyunique. @example @group new value 0 -list was empty, add sentinal +list was empty, add sentinel new value 0 growing the list new value 0 @@ -2527,7 +2527,7 @@ cp .libs/libNumberIO.so _NumberIO.so The first four commands, generate the swig interface file @file{NumberIO.i} and python wrap files @file{NumberIO_wrap.cxx} and -@file{NumberIO.py}. The next three @file{libtool} commnads compile +@file{NumberIO.py}. The next three @file{libtool} commands compile the C++ and Modula-2 source code into @file{.lo} objects. The last @file{libtool} command links all the @file{.lo} files into a @file{.la} file and includes all shared library dependencies. diff --git a/gcc/doc/gty.texi b/gcc/doc/gty.texi index 7c4c48d3ea54..bb853ef3ff05 100644 --- a/gcc/doc/gty.texi +++ b/gcc/doc/gty.texi @@ -252,7 +252,7 @@ from a process reading PCH. @item for_user Use this to mark types that need to be marked by user gc routines, but are not -refered to in a template argument. So if you have some user gc type T1 and a +referred to in a template argument. So if you have some user gc type T1 and a non user gc type T2 you can give T2 the for_user option so that the marking functions for T1 can call non mangled functions to mark T2. diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index 32b0f1cce6be..202edff03408 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -1366,7 +1366,7 @@ specified, then the default set of libraries is selected. profiles respectively. Note that, due to some limitation of the current multilib framework, using the combined @code{aprofile,rmprofile} multilibs selects in some cases a less optimal multilib than when using -the multilib profile for the architecture targetted. The special value +the multilib profile for the architecture targeted. The special value @code{default} is also accepted and is equivalent to omitting the option, i.e., only the default run-time library will be enabled. @@ -4674,7 +4674,7 @@ This configuration is intended for embedded systems. @anchor{mips-x-x} @heading mips-*-* If on a MIPS system you get an error message saying ``does not have gp -sections for all it's [sic] sectons [sic]'', don't worry about it. This +sections for all it's [sic] sections [sic]'', don't worry about it. This happens whenever you use GAS with the MIPS linker, but there is not really anything wrong, and it is okay to use the output file. You can stop such warnings by installing the GNU linker. diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 5374cbbfb6f5..09321ca5da95 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -2139,7 +2139,7 @@ Summing it all up for an intuitive though slightly imprecise data flow: the primary output name is broken into a directory part and a basename part; @var{dumppfx} is set to the former, unless overridden by @option{-dumpdir} or @option{-save-temps=*}, and @var{dumpbase} is set -to the latter, unless overriden by @option{-dumpbase}. If there are +to the latter, unless overridden by @option{-dumpbase}. If there are multiple inputs or linking, this @var{dumpbase} may be combined with @var{dumppfx} and taken from each input file. Auxiliary output names for each input are formed by combining @var{dumppfx}, @var{dumpbase} @@ -12010,7 +12010,7 @@ The analyzer will complain for the above case because if @code{opcode} ever matches none of the cases, the @code{switch} will follow the implicit @code{default} case, making the body of the loop be a ``no-op'' with @code{cpu_state.pc} unchanged, and thus using the same value of -@code{opcode} on all subseqent iterations, leading to an infinite loop. +@code{opcode} on all subsequent iterations, leading to an infinite loop. See @uref{https://cwe.mitre.org/data/definitions/835.html, CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')}. @@ -12031,7 +12031,7 @@ to parameters or globals are assumed to lead to termination of the recursion and thus suppress the warning. This diagnostic is likely to miss cases of infinite recursion that -are convered to iteration by the optimizer before the analyzer "sees" +are converted to iteration by the optimizer before the analyzer "sees" them. Hence optimization should be disabled when attempting to trigger this diagnostic. @@ -27843,7 +27843,7 @@ Set the cost of ADDRESS_REG_REG to the value calculated by @var{n}. @opindex mcheck-zero-division @opindex mno-check-zero-division @item -mcheck-zero-division -@itemx -mno-check-zero-divison +@itemx -mno-check-zero-division Trap (do not trap) on integer division by zero. The default is @option{-mcheck-zero-division} for @option{-O0} or @option{-Og}, and @option{-mno-check-zero-division} for other optimization levels. @@ -28622,7 +28622,7 @@ This option is disabled by default; GCC generates code that assumes that the data segment follows the text segment. @opindex mid-shared-library -@opindex mno-id-shared-libary +@opindex mno-id-shared-library @item -mid-shared-library @itemx -mno-id-shared-library If enabled, generate code that supports shared libraries via the diff --git a/gcc/doc/libgdiagnostics/topics/compatibility.rst b/gcc/doc/libgdiagnostics/topics/compatibility.rst index ff5a9d0d8160..3163e576316a 100644 --- a/gcc/doc/libgdiagnostics/topics/compatibility.rst +++ b/gcc/doc/libgdiagnostics/topics/compatibility.rst @@ -30,7 +30,7 @@ libgdiagnostics.h. locked-down at this time. API compatibility is achieved by extending the API rather than changing -it. For ABI compatiblity, we avoid bumping the SONAME, and instead use +it. For ABI compatibility, we avoid bumping the SONAME, and instead use symbol versioning to tag each symbol, so that a binary linked against libgdiagnostics.so is tagged according to the symbols that it uses. @@ -166,7 +166,7 @@ tagged with ``LIBGDIAGNOSTICS_ABI_0``; these entrypoints are: ``LIBGDIAGNOSTICS_ABI_1`` ------------------------- ``LIBGDIAGNOSTICS_ABI_1`` covers the addition of these functions for -acccessing values within a :type:`diagnostic_logical_location`: +accessing values within a :type:`diagnostic_logical_location`: * :func:`diagnostic_logical_location_get_kind` diff --git a/gcc/doc/libgdiagnostics/topics/physical-locations.rst b/gcc/doc/libgdiagnostics/topics/physical-locations.rst index 06fbaeda0b63..210c66f8d588 100644 --- a/gcc/doc/libgdiagnostics/topics/physical-locations.rst +++ b/gcc/doc/libgdiagnostics/topics/physical-locations.rst @@ -50,7 +50,7 @@ locations. (`SARIF v2.1.0 ยง3.24.10 <https://docs.oasis-open.org/sarif/sarif/v2.1.0/errata01/os/sarif-v2.1.0-errata01-os-complete.html#_Toc141790871>`_). See `SARIF v2.1.0 Appendix J <https://docs.oasis-open.org/sarif/sarif/v2.1.0/errata01/os/sarif-v2.1.0-errata01-os-complete.html#_Toc141791197>`_ - for suggested values for various programmming languages. + for suggested values for various programming languages. For example, this creates a :type:`diagnostic_file` for ``foo.c`` and identifies it as C source code:: diff --git a/gcc/doc/libgdiagnostics/tutorial/07-execution-paths.rst b/gcc/doc/libgdiagnostics/tutorial/07-execution-paths.rst index f1c725b72393..6bb8d1d23ae2 100644 --- a/gcc/doc/libgdiagnostics/tutorial/07-execution-paths.rst +++ b/gcc/doc/libgdiagnostics/tutorial/07-execution-paths.rst @@ -23,7 +23,7 @@ Tutorial part 7: execution paths A :type:`diagnostic` can optionally have a :type:`diagnostic_execution_path` describing a path of execution through code. -For example, let's pretend we're writing a static analyis tool for finding +For example, let's pretend we're writing a static analysis tool for finding bugs in `CPython extension code <https://docs.python.org/3/c-api/index.html>`_. Let's say we're analyzing this code: diff --git a/gcc/doc/libgdiagnostics/tutorial/08-message-buffers.rst b/gcc/doc/libgdiagnostics/tutorial/08-message-buffers.rst index 649a90898f63..e03341ebdcf3 100644 --- a/gcc/doc/libgdiagnostics/tutorial/08-message-buffers.rst +++ b/gcc/doc/libgdiagnostics/tutorial/08-message-buffers.rst @@ -25,7 +25,7 @@ In previous examples, we finished a diagnostic with a call to to determine the text message of the diagnostic. Sometimes this approach is inconvenient, such as where you might want to -build up a message programatically from a series of components. +build up a message programmatically from a series of components. Additionally, you might have existing code that uses ``fprintf``, whereas :func:`diagnostic_finish` has its :doc:`own formatting conventions <../topics/message-formatting>` which are diff --git a/gcc/doc/match-and-simplify.texi b/gcc/doc/match-and-simplify.texi index f02f3b2f872d..b187dd275611 100644 --- a/gcc/doc/match-and-simplify.texi +++ b/gcc/doc/match-and-simplify.texi @@ -234,7 +234,7 @@ preprocessor directives. Here we introduce flags on match expressions. The flag used above, @code{c}, denotes that the expression should -be also matched commutated. Thus the above match expression +be also matched commuted. Thus the above match expression is really the following four match expressions: @smallexample diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi index 94d258c3c919..5a2625ce9861 100644 --- a/gcc/doc/md.texi +++ b/gcc/doc/md.texi @@ -117,7 +117,7 @@ A @code{define_insn} is an RTL expression containing four or five operands: @enumerate @item An optional name @var{n}. When a name is present, the compiler -automically generates a C++ function @samp{gen_@var{n}} that takes +automatically generates a C++ function @samp{gen_@var{n}} that takes the operands of the instruction as arguments and returns the instruction's rtx pattern. The compiler also assigns the instruction a unique code @samp{CODE_FOR_@var{n}}, with all such codes belonging to an enum @@ -2128,7 +2128,7 @@ A signed 12-bit integer constant. @item Cal constant for arithmetic/logical operations. This might be any constant -that can be put into a long immediate by the assmbler or linker without +that can be put into a long immediate by the assembler or linker without involving a PIC relocation. @item K @@ -4289,9 +4289,9 @@ like code motion can lead to cases where code optimized for size uses alternatives that are not preferred for size, and similarly for speed. Although @code{define_insn}s can in principle specify the @code{enabled} -attribute directly, it is often clearer to have subsiduary attributes +attribute directly, it is often clearer to have subsidiary attributes for each architectural feature of interest. The @code{define_insn}s -can then use these subsiduary attributes to say which alternatives +can then use these subsidiary attributes to say which alternatives require which features. The example below does this for @code{cpu_facility}. E.g. the following two patterns could easily be merged using the @code{enabled} @@ -4894,7 +4894,7 @@ Similar, for other arithmetic operations. @mdindex ustrunc@var{m}@var{n}2 @item @samp{ustrunc@var{m}@var{n}2} Truncate the operand 1, and storing the result in operand 0. There will -be saturation during the trunction. The result will be saturated to the +be saturation during the truncation. The result will be saturated to the maximal value of operand 0 type if there is overflow when truncation. The operand 1 must have mode @var{n}, and the operand 0 must have mode @var{m}. Both scalar and vector integer modes are allowed. @@ -6752,7 +6752,7 @@ target can initialize all of the optabs at once with @code{init_sync_libfuncs}. For the purposes of C++11 @code{std::atomic::is_lock_free}, it is assumed that these library calls do @emph{not} use any kind of -interruptable locking. +interruptible locking. @mdindex sync_add@var{mode} @mdindex sync_sub@var{mode} @@ -8121,21 +8121,21 @@ result of a vector boolean can be represented as 0 or -1. @mdindex vec_addsub@var{m}3 @item @samp{vec_addsub@var{m}3} Alternating subtract, add with even lanes doing subtract and odd -lanes doing addition. Operands 1 and 2 and the outout operand are vectors +lanes doing addition. Operands 1 and 2 and the output operand are vectors with mode @var{m}. @mdindex vec_fmaddsub@var{m}4 @item @samp{vec_fmaddsub@var{m}4} Alternating multiply subtract, add with even lanes doing subtract and odd lanes doing addition of the third operand to the multiplication result -of the first two operands. Operands 1, 2 and 3 and the outout operand are vectors +of the first two operands. Operands 1, 2 and 3 and the output operand are vectors with mode @var{m}. @mdindex vec_fmsubadd@var{m}4 @item @samp{vec_fmsubadd@var{m}4} Alternating multiply add, subtract with even lanes doing addition and odd lanes doing subtraction of the third operand to the multiplication result -of the first two operands. Operands 1, 2 and 3 and the outout operand are vectors +of the first two operands. Operands 1, 2 and 3 and the output operand are vectors with mode @var{m}. These instructions are not allowed to @code{FAIL}. @@ -10779,7 +10779,7 @@ The @code{mnemonic} attribute set is not generated automatically if the instruction string is generated via C code. An existing @code{mnemonic} attribute set in an insn definition will not -be overriden by the md file parser. That way it is possible to +be overridden by the md file parser. That way it is possible to manually set the instruction mnemonics for the cases where the md file parser fails to determine it automatically. @@ -11411,7 +11411,7 @@ can be quite tedious to describe these forms directly in the [@var{predicate-pattern}] "@var{condition}" "@var{output-template}" - "@var{optional-insn-attribues}") + "@var{optional-insn-attributes}") @end smallexample @var{predicate-pattern} is the condition that must be true for the @@ -12228,7 +12228,7 @@ Attributes are defined using: (define_int_attr @var{attr_name} [(@var{int1} "@var{value1}") @dots{} (@var{intn} "@var{valuen}")]) @end smallexample -In additon to these user-defined attributes, it is possible to use +In addition to these user-defined attributes, it is possible to use @samp{<@var{name}>} to refer to the current expansion of iterator @var{name} (such as @var{int1}, @var{int2}, and so on). diff --git a/gcc/doc/optinfo.texi b/gcc/doc/optinfo.texi index 15aeaac2486e..d3af459e81f0 100644 --- a/gcc/doc/optinfo.texi +++ b/gcc/doc/optinfo.texi @@ -242,5 +242,5 @@ gcc -fopt-info-vec-missed=vec.miss -fopt-info-loop-optimized=loop.opt Here the two output file names @file{vec.miss} and @file{loop.opt} are in conflict since only one output file is allowed. In this case, only the first option takes effect and the subsequent options are -ignored. Thus only the @file{vec.miss} is produced which containts +ignored. Thus only the @file{vec.miss} is produced which contains dumps from the vectorizer about missed opportunities. diff --git a/gcc/doc/params.texi b/gcc/doc/params.texi index 8d0eb971964f..28cfe73d9d73 100644 --- a/gcc/doc/params.texi +++ b/gcc/doc/params.texi @@ -2073,7 +2073,7 @@ loop. The default value is four. @paindex aarch64-tag-memory-loop-threshold @item aarch64-tag-memory-loop-threshold -Parameter to control the treshold in number of granules beyond which an +Parameter to control the threshold in number of granules beyond which an explicit loop for tagging a memory block is emitted. The memory block is tagged using MTE instructions. diff --git a/gcc/doc/poly-int.texi b/gcc/doc/poly-int.texi index 3cfda422d5ae..dd1f7b0e72e8 100644 --- a/gcc/doc/poly-int.texi +++ b/gcc/doc/poly-int.texi @@ -93,7 +93,7 @@ must be a nonnegative integer. An indeterminate value of 0 should usually represent the minimum possible runtime value, with @var{c0} specifying the value in that case. -For example, when targetting the Arm SVE ISA, the single indeterminate +For example, when targeting the Arm SVE ISA, the single indeterminate represents the number of 128-bit blocks in a vector @emph{beyond the minimum length of 128 bits}. Thus the number of 64-bit doublewords in a vector is 2 + 2 * @var{x1}. If an aggregate has a single SVE vector and 16 @@ -887,7 +887,7 @@ out of range. Return the result as a @item wi::shwi (@var{value}, @var{precision}) Return a @code{poly_int} with the same value as @var{value}, but with the coefficients converted from @code{HOST_WIDE_INT} to @code{wide_int}. -@var{precision} specifies the precision of the @code{wide_int} cofficients; +@var{precision} specifies the precision of the @code{wide_int} coefficients; if this is wider than a @code{HOST_WIDE_INT}, the coefficients of @var{value} will be sign-extended to fit. @@ -1031,7 +1031,7 @@ only needs to be given once. For example: Target-specific code in @file{config/@var{cpu}} only needs to handle non-constant @code{poly_int}s if @code{NUM_POLY_INT_COEFFS} is greater than one. For other targets, @code{poly_int} degenerates to a compile-time -constant and is often interchangable with a normal scalar integer. +constant and is often interchangeable with a normal scalar integer. There are two main exceptions: @itemize diff --git a/gcc/doc/riscv-ext.texi b/gcc/doc/riscv-ext.texi index bf4f56a62012..dd00dc154be4 100644 --- a/gcc/doc/riscv-ext.texi +++ b/gcc/doc/riscv-ext.texi @@ -728,7 +728,7 @@ @item @samp{xandesperf} @tab 5.0 -@tab Andes performace extension +@tab Andes performance extension @item @samp{xandesbfhcvt} @tab 5.0 diff --git a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi index 7fd656b70dc3..082cb39372bc 100644 --- a/gcc/doc/rtl.texi +++ b/gcc/doc/rtl.texi @@ -4430,7 +4430,7 @@ using namespace rtl_ssa; However, this is purely a matter of taste, and the examples in the rest of this section do not require it. -The RTL SSA represention is an optional on-the-side feature that applies +The RTL SSA representation is an optional on-the-side feature that applies on top of the normal RTL instructions. It is currently local to individual RTL passes and is not maintained across passes. @@ -4520,7 +4520,7 @@ structures and the underlying CFG @code{basic_block} structures @cindex ``real'' instructions, RTL SSA @anchor{real RTL SSA insns} If a CFG basic block @var{bb} contains an RTL instruction @var{insn}, -the RTL SSA represenation of @var{bb} also contains an RTL SSA representation +the RTL SSA representation of @var{bb} also contains an RTL SSA representation of @var{insn}@footnote{Note that this excludes non-instruction things like @code{note}s and @code{barrier}s that also appear in the chain of RTL instructions.}. Within RTL SSA, these instructions are referred to as diff --git a/gcc/doc/sourcebuild.texi b/gcc/doc/sourcebuild.texi index 6badae4f7745..c12771acd2bc 100644 --- a/gcc/doc/sourcebuild.texi +++ b/gcc/doc/sourcebuild.texi @@ -3612,7 +3612,7 @@ assembler output, excluding LTO sections. @item scan-assembler-bound @var{regex} @var{cmp} @var{num} [@{ target/xfail @var{selector} @}] Passes if @var{regex} is matched @var{cmp} @var{num} times in the test's -assembler output, excluding LTO sections. @var{cmp} is a comparitor. +assembler output, excluding LTO sections. @var{cmp} is a comparator. @item scan-assembler-dem @var{regex} [@{ target/xfail @var{selector} @}] Passes if @var{regex} matches text in the test's demangled assembler output, diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi index 04537aa32006..3e8a44cee74e 100644 --- a/gcc/doc/tm.texi +++ b/gcc/doc/tm.texi @@ -1039,7 +1039,7 @@ applied. @var{type} is either @code{EXCESS_PRECISION_TYPE_IMPLICIT}, @code{EXCESS_PRECISION_TYPE_STANDARD}, or @code{EXCESS_PRECISION_TYPE_FLOAT16}. For @code{EXCESS_PRECISION_TYPE_IMPLICIT}, the target should return which -precision and range operations will be implictly evaluated in regardless +precision and range operations will be implicitly evaluated in regardless of the excess precision explicitly added. For @code{EXCESS_PRECISION_TYPE_STANDARD}, @code{EXCESS_PRECISION_TYPE_FLOAT16}, and @@ -1695,7 +1695,7 @@ the target machine. If you don't define this, the default is @defmac LIBGCC2_GNU_PREFIX This macro corresponds to the @code{TARGET_LIBFUNC_GNU_PREFIX} target -hook and should be defined if that hook is overriden to be true. It +hook and should be defined if that hook is overridden to be true. It causes function names in libgcc to be changed to use a @code{__gnu_} prefix for their name rather than the default @code{__}. A port which uses this macro should also arrange to use @file{t-gnu-prefix} in @@ -4743,7 +4743,7 @@ Define this to return true if the @code{_Float@var{n}} and built-in function without the @code{__builtin_} prefix in addition to the normal built-in function with the @code{__builtin_} prefix. The default is to only enable built-in functions without the @code{__builtin_} prefix for -the GNU C langauge. In strict ANSI/ISO mode, the built-in function without +the GNU C language. In strict ANSI/ISO mode, the built-in function without the @code{__builtin_} prefix is not enabled. The argument @code{FUNC} is the @code{enum built_in_function} id of the function to be enabled. @end deftypefn @@ -6465,7 +6465,7 @@ for a given element mode. The modes returned in @var{modes} should use the smallest element mode possible for the vectorization approach that they represent, preferring -integer modes over floating-poing modes in the event of a tie. The first +integer modes over floating-point modes in the event of a tie. The first mode should be the @code{TARGET_VECTORIZE_PREFERRED_SIMD_MODE} for its element mode. @@ -6693,7 +6693,7 @@ way. @deftypefn {Target Hook} rtx TARGET_GOACC_EXPAND_VAR_DECL (tree @var{var}) This hook, if defined, is used by accelerator target back-ends to expand specially handled kinds of @code{VAR_DECL} expressions. A particular use is -to place variables with specific attributes inside special accelarator +to place variables with specific attributes inside special accelerator memories. A return value of @code{NULL} indicates that the target does not handle this @code{VAR_DECL}, and normal RTL expanding is resumed. @@ -10115,7 +10115,7 @@ specially named labels. The collect2 process will locate these labels and generate code to register the frames. This might be necessary, for instance, if the system linker will not -place the eh_frames in-between the sentinals from @file{crtstuff.c}, +place the eh_frames in-between the sentinels from @file{crtstuff.c}, or if the system linker does garbage collection and sections cannot be marked as not to be collected. @end defmac @@ -12459,7 +12459,7 @@ hardware count register support for decrement and branch, it may have to move IV value from hardware count register to general purpose register while doloop IV candidate is used for address IV uses. It probably takes expensive penalty. This hook allows target owners to define the cost for -this escpecially for address IV uses. +this especially for address IV uses. The default value is zero. @end deftypevr @@ -12612,11 +12612,11 @@ modes and they have different conditional execution capability, such as ARM. @deftypefn {Target Hook} rtx TARGET_GEN_CCMP_FIRST (rtx_insn **@var{prep_seq}, rtx_insn **@var{gen_seq}, rtx_code @var{code}, tree @var{op0}, tree @var{op1}) This function prepares to emit a comparison insn for the first compare in a - sequence of conditional comparisions. It returns an appropriate comparison + sequence of conditional comparisons. It returns an appropriate comparison with @code{CC} for passing to @code{gen_ccmp_next} or @code{cbranch_optab}. The insns to prepare the compare are saved in @var{prep_seq} and the compare insns are saved in @var{gen_seq}. They will be emitted when all the - compares in the conditional comparision are generated without error. + compares in the conditional comparison are generated without error. @var{code} is the @code{rtx_code} of the compare for @var{op0} and @var{op1}. @end deftypefn @@ -12626,7 +12626,7 @@ This function prepares to emit a conditional comparison within a sequence @code{CC} for passing to @code{gen_ccmp_next} or @code{cbranch_optab}. The insns to prepare the compare are saved in @var{prep_seq} and the compare insns are saved in @var{gen_seq}. They will be emitted when all the - compares in the conditional comparision are generated without error. The + compares in the conditional comparison are generated without error. The @var{prev} expression is the result of a prior call to @code{gen_ccmp_first} or @code{gen_ccmp_next}. It may return @code{NULL} if the combination of @var{prev} and this comparison is not supported, otherwise the result must @@ -12981,7 +12981,7 @@ This hook is used to determine the level of target support for compilation for the second case. For targets that have no processors that can execute instructions - speculatively an alternative implemenation of this hook is available: + speculatively an alternative implementation of this hook is available: simply redefine this hook to @code{speculation_safe_value_not_needed} along with your other target hooks. @end deftypefn diff --git a/gcc/doc/tm.texi.in b/gcc/doc/tm.texi.in index e31d7440b75a..3b8b05fed820 100644 --- a/gcc/doc/tm.texi.in +++ b/gcc/doc/tm.texi.in @@ -1430,7 +1430,7 @@ the target machine. If you don't define this, the default is @defmac LIBGCC2_GNU_PREFIX This macro corresponds to the @code{TARGET_LIBFUNC_GNU_PREFIX} target -hook and should be defined if that hook is overriden to be true. It +hook and should be defined if that hook is overridden to be true. It causes function names in libgcc to be changed to use a @code{__gnu_} prefix for their name rather than the default @code{__}. A port which uses this macro should also arrange to use @file{t-gnu-prefix} in @@ -6587,7 +6587,7 @@ specially named labels. The collect2 process will locate these labels and generate code to register the frames. This might be necessary, for instance, if the system linker will not -place the eh_frames in-between the sentinals from @file{crtstuff.c}, +place the eh_frames in-between the sentinels from @file{crtstuff.c}, or if the system linker does garbage collection and sections cannot be marked as not to be collected. @end defmac diff --git a/gcc/doc/tree-ssa.texi b/gcc/doc/tree-ssa.texi index c49994e6968f..052df5383db3 100644 --- a/gcc/doc/tree-ssa.texi +++ b/gcc/doc/tree-ssa.texi @@ -385,7 +385,7 @@ a controlled position, and then iterating over those uses. Then the optimization can manipulate the stmt when all the uses have been processed. Only the current active @code{imm_use_p} may be altered when using an inner @code{FOR_EACH_IMM_USE_ON_STMT} iteration. -You have to be careful to not inadvertedly modify the immediate +You have to be careful to not inadvertently modify the immediate use list by working on another stmt than the the current @code{stmt} during the iteration. In particular calling @code{update_stmt} is destructive on all SSA uses immediate use lists related to the updated stmt.
