This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".
The branch, master has been updated
via c1594fa5dda412c98f3193ca8f993f6fc21e73c1 (commit)
from d0ff325b9f7d8e9462cda905c918f110c02c764b (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit c1594fa5dda412c98f3193ca8f993f6fc21e73c1
Author: Gerald Pfeifer <ger...@pfeifer.com>
Date: Sun May 19 18:13:12 2024 +0200
gcc-14: Fix seven typos
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index dd3fea8d..6447898e 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -31,7 +31,7 @@ You may also want to check out our
another structure, is deprecated. Refer to
<a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Zero-Length.html";>
Zero Length Arrays</a>.
- Any code relying on this extension should be modifed to ensure that
+ Any code relying on this extension should be modified to ensure that
C99 flexible array members only end up at the ends of structures.
Please use the warning option
<a
href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Warning-Options.html#index-Wflex-array-member-not-at-end";><code>-Wflex-array-member-not-at-end</code></a>
to
@@ -111,7 +111,7 @@ You may also want to check out our
properties of functions and variables. The stack frame used by
functions marked with the attribute gets zeroed-out upon returning
or exception escaping. Scalar variables marked with the attribute
- cause functions contaning or accessing them to get stack scrubbing
+ cause functions containing or accessing them to get stack scrubbing
enabled implicitly.
</li>
<li>
@@ -155,7 +155,7 @@ You may also want to check out our
</pre>
can now be vectorized on a number of targets. In this first version any
input data sources must either have a statically known size at compile
time
- or the vectorizer must be able to determine based on auxillary
information
+ or the vectorizer must be able to determine based on auxiliary
information
that the accesses are aligned.
</li>
</ul>
@@ -191,7 +191,7 @@ You may also want to check out our
used for allocatables and pointers using the <code>allocate</code>
directive and its OpenMP 5.2 replacement, the <code>allocators</code>
directive; files using this allocator and all files that might directly
- or indirectly (intrinisic assignment, <code>intent(out)</code>, ...)
+ or indirectly (intrinsic assignment, <code>intent(out)</code>, ...)
de- or reallocate such-allocated variables must be compiled with the
<a
href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gfortran/Fortran-Dialect-Options.html#index-fopenmp-allocators";
><code>-fopenmp-allocators</code></a> option.
@@ -282,7 +282,7 @@ You may also want to check out our
with SPARK 2014.</li>
<li>Support for the <code>LoongArch</code> architecture.</li>
<li>Support for vxWorks 7 Cert RTP has been removed.</li>
- <li>Additional hardening improvements. For more information reltated to
+ <li>Additional hardening improvements. For more information related to
hardening options, refer to
the <a
href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Instrumentation-Options.html#index-fharden-compares";>GCC
Instrumentation Options</a> and
@@ -428,7 +428,7 @@ You may also want to check out our
</li>
<li>
<!-- commit r14-4388-g1c45319b66edc9 -->
- When a diagnostic occurrs involving a C++ template,
+ When a diagnostic occurs involving a C++ template,
GCC will now quote the source code of the context at which
the template is instantiated ("<code>required from here</code>"),
rather than just print filename and line/column numbers.
@@ -1570,7 +1570,7 @@ it emits:
GCC diagnostics have been able to have execution paths associated
with them since GCC 10, but previously these were required to be
single-threaded.
- As of GCC 14, these execution paths can have multipled named threads
+ As of GCC 14, these execution paths can have multiple named threads
associated with them, with each event being associated with one of the
threads.
No existing GCC diagnostics take advantage of this, but GCC plugins
-----------------------------------------------------------------------
Summary of changes:
htdocs/gcc-14/changes.html | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
hooks/post-receive
--
gcc-wwwdocs
