public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
* gcc-wwwdocs branch master updated. 8095e54fa7c659dc5b00ddc4ff4e48a30dfaa1f2
@ 2024-05-07  6:34 Jakub Jelinek
  0 siblings, 0 replies; only message in thread
From: Jakub Jelinek @ 2024-05-07  6:34 UTC (permalink / raw)
  To: gcc-cvs-wwwdocs

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 30266 bytes --]

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  8095e54fa7c659dc5b00ddc4ff4e48a30dfaa1f2 (commit)
      from  b018ddd6e4b85c37ea3129b567c1f67717a40132 (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 8095e54fa7c659dc5b00ddc4ff4e48a30dfaa1f2
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue May 7 08:32:45 2024 +0200

    Adjust onlinedocs references to 14.1.0.

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 82906de1..28e5da9f 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -32,12 +32,12 @@ a work-in-progress.</p>
       Support for the GCC extension, a structure containing a C99 flexible array
       member, or a union containing such a structure, is not the last field of
       another structure, is deprecated. Refer to
-      <a href="https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html">
+      <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
       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/Warning-Options.html#index-Wflex-array-member-not-at-end"><code>-Wflex-array-member-not-at-end</code></a> to
+      <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
       identify all such cases in the source code and modify them.
   </li>
   <li><strong>C:</strong>
@@ -45,7 +45,7 @@ a work-in-progress.</p>
       <a href="porting_to.html#warnings-as-errors">Porting to GCC 14</a>
       for details.
   </li>
-  <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html"><code>-fcf-protection=[full|branch|return|none|check]</code></a>
+  <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Instrumentation-Options.html"><code>-fcf-protection=[full|branch|return|none|check]</code></a>
       is refactored, to override <code>-fcf-protection</code>,
       <code>-fcf-protection=none</code> needs to be added and then
       with <code>-fcf-protection=xxx</code>.
@@ -58,7 +58,7 @@ a work-in-progress.</p>
       declared obsolete in GCC 14, and the sources will also be removed
       in the next release of GCC.
   </li>
-  <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html"><code>-fanalyzer</code></a>
+  <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html"><code>-fanalyzer</code></a>
     is still only suitable for analyzing C code.
     In particular, using it on C++ is unlikely to give meaningful output.
   </li>
@@ -74,7 +74,7 @@ a work-in-progress.</p>
       when the user or compiler links them on the host side. Thus, it is no
       longer required to explicitly pass <code>-lm</code> and/or
       <code>-lgfortran</code> to the offload-device linker using the <a
-      href="https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html#index-foffload-options"
+      href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/C-Dialect-Options.html#index-foffload-options"
       ><code>-foffload-options=</code></a> flag.
   </li>
   <li>
@@ -85,14 +85,14 @@ a work-in-progress.</p>
   </li>
   <li>
     New option
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html#index-fhardened"><code>-fhardened</code></a>,
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Instrumentation-Options.html#index-fhardened"><code>-fhardened</code></a>,
     an umbrella option that enables a set of hardening flags.
     The options it enables can be displayed using the
     <code>--help=hardened</code> option.
   </li>
   <li>
     New option
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html#index-fharden-control-flow-redundancy"><code>-fharden-control-flow-redundancy</code></a>,
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Instrumentation-Options.html#index-fharden-control-flow-redundancy"><code>-fharden-control-flow-redundancy</code></a>,
     to verify, at the end of functions, that the visited basic blocks
     correspond to a legitimate execution path, so as to detect and
     prevent attacks that transfer control into the middle of
@@ -100,7 +100,7 @@ a work-in-progress.</p>
   </li>
   <li>
     New type attribute
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Type-Attributes.html#index-hardbool-type-attribute"><code>hardbool</code></a>,
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Common-Type-Attributes.html#index-hardbool-type-attribute"><code>hardbool</code></a>,
     for C and Ada.  Hardened
     booleans take user-specified representations for <code>true</code>
     and <code>false</code>, presumably with higher hamming distance
@@ -109,7 +109,7 @@ a work-in-progress.</p>
   </li>
   <li>
     New type attribute
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Type-Attributes.html#index-strub-type-attribute"><code>strub</code></a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Common-Type-Attributes.html#index-strub-type-attribute"><code>strub</code></a>
     to control stack scrubbing
     properties of functions and variables.  The stack frame used by
     functions marked with the attribute gets zeroed-out upon returning
@@ -119,7 +119,7 @@ a work-in-progress.</p>
   </li>
   <li>
     New option
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-finline-stringops"><code>-finline-stringops</code></a>,
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Optimize-Options.html#index-finline-stringops"><code>-finline-stringops</code></a>,
     to force inline
     expansion of <code>memcmp</code>, <code>memcpy</code>,
     <code>memmove</code> and <code>memset</code>, even when that is
@@ -129,7 +129,7 @@ a work-in-progress.</p>
   <li>
     <!-- commit r14-4958-gcd7dadcd2759d1 -->
     New function attribute
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-null_005fterminated_005fstring_005farg-function-attribute"> <code>null_terminated_string_arg(<i>PARAM_IDX</i>)</code></a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Common-Function-Attributes.html#index-null_005fterminated_005fstring_005farg-function-attribute"> <code>null_terminated_string_arg(<i>PARAM_IDX</i>)</code></a>
     for indicating parameters that are expected to be null-terminated
     strings.
   </li>
@@ -287,7 +287,7 @@ a work-in-progress.</p>
   <li>Support for vxWorks 7 Cert RTP has been removed.</li>
   <li>Additional hardening improvements. For more information reltated to
     hardening options, refer to
-    the <a href="https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html#index-fharden-compares">GCC
+    the <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Instrumentation-Options.html#index-fharden-compares">GCC
     Instrumentation Options</a> and
     the <a href="https://gcc.gnu.org/onlinedocs/gnat_rm/Security-Hardening-Features.html">GNAT
     Reference Manual, Security and Hardening Features</a>.
@@ -446,7 +446,7 @@ a work-in-progress.</p>
       warning does not warn about <code>std::span</code>-like classes; there is
       also a new attribute <code>gnu::no_dangling</code> to suppress the
       warning.  See
-      <a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-Wdangling-reference">the manual</a>
+      <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/C_002b_002b-Dialect-Options.html#index-Wdangling-reference">the manual</a>
       for more info.</li>
   <li><em>noexcept(expr)</em> is now mangled as per the Itanium ABI</li>
   <li>the named return value optimization can now be performed even for
@@ -456,7 +456,7 @@ a work-in-progress.</p>
   <li>New <code>-Wnrvo</code> warning, to warn if the named return value
       optimization is not performed although it is allowed by
       [class.copy.elision].  See
-      <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wnrvo">the manual</a>
+      <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Warning-Options.html#index-Wnrvo">the manual</a>
       for more info.</li>
   <li>The backing array for <code>std::initializer_list</code> has been made
       static, allowing combining multiple equivalent initializer-lists
@@ -500,7 +500,7 @@ a work-in-progress.</p>
       (<a href="https://gcc.gnu.org/PR18474">PR18474</a>)</li>
   <li>Attributes <code>hot</code> and <code>cold</code> can be applied to
       classes as well.  See
-      <a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Attributes.html#index-cold-type-attribute">the manual</a>
+      <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/C_002b_002b-Attributes.html#index-cold-type-attribute">the manual</a>
       for more info.</li>
   <li>Function template constraints, as well as CTAD placeholders, are
       now mangled</li>
@@ -748,7 +748,7 @@ a work-in-progress.</p>
     </ul></li>
   <li>The option <code>-mtp=</code> is now supported for changing the TPIDR
    register used for TLS accesses.  For more details please refer to the
-   <a href="https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html">
+   <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/AArch64-Options.html">
    documentation</a>.</li>
 </ul>
 
@@ -856,9 +856,9 @@ __asm (".global __flmap_lock"  "\n\t"
     The default is to locate read-only data in program memory for devices that
     support it, e.g. for AVR64* and AVR128* devices as explained above,
     and for devices from the
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/AVR-Options.html#avrxmega3">avrxmega3</a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/AVR-Options.html#avrxmega3">avrxmega3</a>
     and
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/AVR-Options.html#avrtiny">avrtiny</a> families.
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/AVR-Options.html#avrtiny">avrtiny</a> families.
   </li>
   <li>The new built-in macro <code>__AVR_RODATA_IN_RAM__</code> is supported
     on all devices. It's defined to  <code>0</code> or <code>1</code>.
@@ -866,7 +866,7 @@ __asm (".global __flmap_lock"  "\n\t"
   <li>
     A new optimization tries to improve code generation for indirect memory
     accesses on
-     <a href="https://gcc.gnu.org/onlinedocs/gcc/AVR-Options.html#avrtiny"
+     <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/AVR-Options.html#avrtiny"
 	>Reduced Tiny devices</a>.
      It can be controlled by the new compiler option
      <code>-mfuse-add=<var>level</var></code> where <var>level</var>
@@ -977,7 +977,7 @@ __asm (".global __flmap_lock"  "\n\t"
 <h3 id="loongarch">LoongArch</h3>
 <ul>
   <li>Support for the following
-      <a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-march-7">
+      <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-march-7">
       <code>-march</code></a> parameters has been added:
       <ul>
         <li><code>la64v1.0</code></li>
@@ -991,7 +991,7 @@ __asm (".global __flmap_lock"  "\n\t"
       Toolchain Conventions of the LoongArch™ Architecture</a>.
   </li>
   <li>Support for the following
-      <a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-mtune-8">
+      <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-mtune-8">
       <code>-mtune</code></a> parameters has been added:
       <ul>
         <li><code>generic</code></li>
@@ -1056,59 +1056,59 @@ __asm (".global __flmap_lock"  "\n\t"
   </li>
   <li>New Intrinsics
     <ul>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Base-Built-in-Functions.html">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Base-Built-in-Functions.html">
           <code>__builtin_thread_pointer</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-SX-Vector-Intrinsics.html">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-SX-Vector-Intrinsics.html">
           <code>__lsx_*</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-ASX-Vector-Intrinsics.html">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-ASX-Vector-Intrinsics.html">
           <code>__lasx_*</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Base-Built-in-Functions.html">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Base-Built-in-Functions.html">
           <code>__frecipe_{s/d}</code> and <code>__frsqrte_{s/d}</code></a>
       </li>
     </ul>
   </li>
   <li>New Compiler Option
     <ul>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-ml_005ba_005dsx">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-ml_005ba_005dsx">
           <code>-m[no-]lsx</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-ml_005ba_005dsx">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-ml_005ba_005dsx">
           <code>-m[no-]lasx</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-mfrecipe">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-mfrecipe">
           <code>-m[no-]frecipe</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-mdiv32">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-mdiv32">
           <code>-m[no-]div32</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-mlam-bh">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-mlam-bh">
           <code>-m[no-]lam-bh</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-mlamcas">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-mlamcas">
           <code>-m[no-]lamcas</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-mld-seq-sa">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-mld-seq-sa">
           <code>-m[no-]ld-seq-sa</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-mrecip_003dopt">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-mrecip_003dopt">
           <code>-mrecip=</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-mrecip">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-mrecip">
           <code>-m[no-]recip</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-mexplicit-relocs-1">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-mexplicit-relocs-1">
           <code>-mexplicit-relocs={none,always,auto}</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-mrelax-2">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-mrelax-2">
           <code>-m[no-]relax</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-mpass-mrelax-to-as">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-mpass-mrelax-to-as">
           <code>-m[no-]pass-mrelax-to-as</code></a>
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-mtls-dialect-1">
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-mtls-dialect-1">
           <code>-mtls-dialect={trad,desc}</code></a>
       </li>
     </ul>
@@ -1125,7 +1125,7 @@ __asm (".global __flmap_lock"  "\n\t"
   <li>Optimizing built-in functions for memory-model-aware atomic operations
       using hierarchical dbar instructions.</li>
   <li>TLS descriptors support. It is not enabled by default, and can be enabled
-      with <a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Options.html#index-mtls-dialect-1">
+      with <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/LoongArch-Options.html#index-mtls-dialect-1">
       <code>-mtls-dialect=desc</code></a>. The default behavior can be
       configured with <code>--with-tls=[trad|desc]</code>.</li>
 </ul>
@@ -1369,16 +1369,16 @@ __asm (".global __flmap_lock"  "\n\t"
     <ul>
       <li>
 	<!-- commit r14-5566-g841008d3966c0f [PR106147] -->
-	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-infinite-loop"><code>-Wanalyzer-infinite-loop</code></a>
+	<a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-Wanalyzer-infinite-loop"><code>-Wanalyzer-infinite-loop</code></a>
 	warns about paths through the code which appear to lead to an infinite loop.
       </li>
       <li>
 	<!-- commit r14-3556-g034d99e81484fb [PR99860] -->
-	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-overlapping-buffers"><code>-Wanalyzer-overlapping-buffers</code></a> warns for paths through the code in which overlapping buffers are passed to an API for which the behavior on such buffers is undefined.
+	<a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-Wanalyzer-overlapping-buffers"><code>-Wanalyzer-overlapping-buffers</code></a> warns for paths through the code in which overlapping buffers are passed to an API for which the behavior on such buffers is undefined.
       </li>
       <li>
 	<!-- commit r14-5591-gf65f63c4d86a48 [PR107573] -->
-	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-undefined-behavior-strtok"><code>-Wanalyzer-undefined-behavior-strtok</code></a>
+	<a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-Wanalyzer-undefined-behavior-strtok"><code>-Wanalyzer-undefined-behavior-strtok</code></a>
 	warns for paths through the code in which a call is made to
 	<code>strtok</code> with undefined behavior.
       </li>
@@ -1387,30 +1387,30 @@ __asm (".global __flmap_lock"  "\n\t"
   <li>
     <!-- commit r14-5464-gcfaaa8b11b8429 [PR103533] -->
     Previously, the analyzer's "taint" tracking to be explicitly enabled via
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-fanalyzer-checker"><code>-fanalyzer-checker=taint</code></a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-fanalyzer-checker"><code>-fanalyzer-checker=taint</code></a>
     (along with
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-fanalyzer"><code>-fanalyzer</code></a>).
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-fanalyzer"><code>-fanalyzer</code></a>).
     This is now enabled by default when
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-fanalyzer"><code>-fanalyzer</code></a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-fanalyzer"><code>-fanalyzer</code></a>
     is selected, thus also enabling the 6 taint-based warnings:
     <ul>
       <li>
-	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-tainted-allocation-size"><code>-Wanalyzer-tainted-allocation-size</code></a>
+	<a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-Wanalyzer-tainted-allocation-size"><code>-Wanalyzer-tainted-allocation-size</code></a>
       </li>
       <li>
-	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-tainted-array-index"><code>-Wanalyzer-tainted-array-index</code></a>
+	<a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-Wanalyzer-tainted-array-index"><code>-Wanalyzer-tainted-array-index</code></a>
       </li>
       <li>
-	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-tainted-assertion"><code>-Wanalyzer-tainted-assertion</code></a>
+	<a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-Wanalyzer-tainted-assertion"><code>-Wanalyzer-tainted-assertion</code></a>
       </li>
       <li>
-	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-tainted-divisor"><code>-Wanalyzer-tainted-divisor</code></a>
+	<a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-Wanalyzer-tainted-divisor"><code>-Wanalyzer-tainted-divisor</code></a>
       </li>
       <li>
-	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-tainted-offset"><code>-Wanalyzer-tainted-offset</code></a>
+	<a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-Wanalyzer-tainted-offset"><code>-Wanalyzer-tainted-offset</code></a>
       </li>
       <li>
-	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-tainted-size"><code>-Wanalyzer-tainted-size</code></a>
+	<a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-Wanalyzer-tainted-size"><code>-Wanalyzer-tainted-size</code></a>
       </li>
     </ul>
   </li>
@@ -1422,10 +1422,10 @@ __asm (".global __flmap_lock"  "\n\t"
     a read of an uninitialized byte or an out-of-range accesses seen
     before any zero byte is seen.
     This applies to functions that use the new
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-null_005fterminated_005fstring_005farg-function-attribute"> <code>null_terminated_string_arg(<i>PARAM_IDX</i>)</code></a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Common-Function-Attributes.html#index-null_005fterminated_005fstring_005farg-function-attribute"> <code>null_terminated_string_arg(<i>PARAM_IDX</i>)</code></a>
     attribute, <!-- commit r14-4958-gcd7dadcd2759d1 -->
     functions that use the
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-format-function-attribute"><code>format</code></a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Common-Function-Attributes.html#index-format-function-attribute"><code>format</code></a>
     attribute, <!-- commit r14-3376-g3b691e0190c6e7 -->
     and to the library functions
     <code>error</code> (parameter 3),
@@ -1437,14 +1437,14 @@ __asm (".global __flmap_lock"  "\n\t"
   <li>
     <!-- commit r14-3001-g021077b94741c9 [PR110426] -->
     The analyzer now makes use of the function attribute
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-alloc_005fsize-function-attribute"><code>alloc_size</code></a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Common-Function-Attributes.html#index-alloc_005fsize-function-attribute"><code>alloc_size</code></a>
     allowing
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-fanalyzer"><code>-fanalyzer</code></a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-fanalyzer"><code>-fanalyzer</code></a>
     to emit
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-allocation-size"><code>-Wanalyzer-allocation-size</code></a>,
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-out-of-bounds"><code>-Wanalyzer-out-of-bounds</code></a>,
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-Wanalyzer-allocation-size"><code>-Wanalyzer-allocation-size</code></a>,
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-Wanalyzer-out-of-bounds"><code>-Wanalyzer-out-of-bounds</code></a>,
     and
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-tainted-allocation-size"><code>-Wanalyzer-tainted-allocation-size</code></a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-Wanalyzer-tainted-allocation-size"><code>-Wanalyzer-tainted-allocation-size</code></a>
     on execution paths involving allocations using such functions.
   </li>
   <li>
@@ -1464,7 +1464,7 @@ __asm (".global __flmap_lock"  "\n\t"
   <li>
     <!-- commit r14-2029-g0e466e978c7286 [PR106626] -->
       The warning
-      <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-out-of-bounds"><code>-Wanalyzer-out-of-bounds</code></a>
+      <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Static-Analyzer-Options.html#index-Wanalyzer-out-of-bounds"><code>-Wanalyzer-out-of-bounds</code></a>
       has been extended so that, where possible, it will emit a text-based
       diagram visualizing the spatial relationship between
       <ol>
@@ -1477,7 +1477,7 @@ __asm (".global __flmap_lock"  "\n\t"
       the direction of the access (read vs write), and, in some cases,
       the values of data involved.
     <p>Such "text art" diagrams can be controlled (or suppressed) via a new
-      <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-text-art-charset"><code>-fdiagnostics-text-art-charset=</code></a> option.
+      <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-text-art-charset"><code>-fdiagnostics-text-art-charset=</code></a> option.
     <p>For example, given the out-of-bounds write in <code>strcat</code> in:
       <!-- commit r14-4477-gb365e9d57ad445 -->
 <pre>
@@ -1529,17 +1529,17 @@ it emits:
   <li>
     <!-- commit r14-6228-g3bd8241a1f1982 -->
     The SARIF output from
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format"><code>-fdiagnostics-format=</code></a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format"><code>-fdiagnostics-format=</code></a>
     now adds indentation and newlines to reflect the logical JSON structure of the data.  The previous compact behavior can be restored via the new option
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fno-diagnostics-json-formatting"><code>-fno-diagnostics-json-formatting</code></a>.
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Diagnostic-Message-Formatting-Options.html#index-fno-diagnostics-json-formatting"><code>-fno-diagnostics-json-formatting</code></a>.
     This also applies to the older output format named "json".
   </li>
   <li>
     <!-- commit r14-2881-g75d623946d4b6e [PR109361] -->
     If profiling information about the compiler itself is requested via
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Developer-Options.html#index-ftime-report"><code>-ftime-report</code></a>,
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Developer-Options.html#index-ftime-report"><code>-ftime-report</code></a>,
     and a SARIF output format is requested via
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format"><code>-fdiagnostics-format=</code></a>,
+    <a href="https://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format"><code>-fdiagnostics-format=</code></a>,
     then the timing and memory usage data is now written in JSON form into
     the SARIF output, rather than as plain text to stderr.
   </li>
diff --git a/htdocs/gcc-14/index.html b/htdocs/gcc-14/index.html
index 3ecd1693..c8a9cb34 100644
--- a/htdocs/gcc-14/index.html
+++ b/htdocs/gcc-14/index.html
@@ -22,7 +22,7 @@ GNU Compiler Collection.</p>
 <p>The GCC developers would like to thank the numerous people that have
 contributed new features, improvements, bug fixes, and other changes as
 well as test results to GCC.
-This <a href="http://gcc.gnu.org/onlinedocs/gcc/Contributors.html">amazing
+This <a href="http://gcc.gnu.org/onlinedocs/gcc-14.1.0/gcc/Contributors.html">amazing
 group of volunteers</a> is what makes GCC successful.</p>
 
 <p>For additional information about GCC please refer to the
diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html
index db27f122..ef02e071 100644
--- a/htdocs/gcc-14/porting_to.html
+++ b/htdocs/gcc-14/porting_to.html
@@ -428,7 +428,7 @@ exec /usr/bin/gcc -fpermissive "$@"
 
 C code generators that cannot be updated to generate valid standard C
 can emit
-<a href="/onlinedocs/gcc/Diagnostic-Pragmas.html"><code>#pragma GCC diagnostic warning</code></a>
+<a href="/onlinedocs/gcc-14.1.0/gcc/Diagnostic-Pragmas.html"><code>#pragma GCC diagnostic warning</code></a>
 directives to turn these errors back into warnings:
 
 <pre>

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-14/changes.html    | 128 +++++++++++++++++++++---------------------
 htdocs/gcc-14/index.html      |   2 +-
 htdocs/gcc-14/porting_to.html |   2 +-
 3 files changed, 66 insertions(+), 66 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2024-05-07  6:34 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-05-07  6:34 gcc-wwwdocs branch master updated. 8095e54fa7c659dc5b00ddc4ff4e48a30dfaa1f2 Jakub Jelinek

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).