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 d9de5c1ccfad4a962287fe8295ee82c0a47d7e37 (commit)
via 6de89e0922c10c33021ce000b0ce630a25005b47 (commit)
from 83ae4dd7ec69490a2b86ef7e1218628889ad57c0 (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 d9de5c1ccfad4a962287fe8295ee82c0a47d7e37
Author: Jakub Jelinek <[email protected]>
Date: Thu Apr 30 10:29:37 2026 +0200
Releasing 16.1.
diff --git a/htdocs/gcc-16/changes.html b/htdocs/gcc-16/changes.html
index 37d5578b..41cf540d 100644
--- a/htdocs/gcc-16/changes.html
+++ b/htdocs/gcc-16/changes.html
@@ -22,9 +22,6 @@ You may also want to check out our
<a href="../onlinedocs/index.html#current">full GCC documentation</a>.
</p>
-<p>Note: GCC 16 has not been released yet, so this document is
-a work-in-progress.</p>
-
<!-- .................................................................. -->
<h2>Caveats</h2>
<ul>
@@ -954,7 +951,15 @@ struct Affected : E
<!-- <h3 id="uninitialized">Eliminating uninitialized variables</h3> -->
<!-- .................................................................. -->
-<!-- <h2 id="16.1">GCC 16.1</a></h2> -->
+<h2 id="16.1">GCC 16.1</h2>
+
+<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=16.0";>list
+of problem reports (PRs)</a> from GCC's bug tracking system that are
+known to be fixed in the 16.1 release. This list might not be
+complete (that is, it is possible that some PRs that have been fixed
+are not listed here).</p>
+
+<!-- .................................................................. -->
</body>
</html>
diff --git a/htdocs/gcc-16/index.html b/htdocs/gcc-16/index.html
index de308c4b..6da3dd83 100644
--- a/htdocs/gcc-16/index.html
+++ b/htdocs/gcc-16/index.html
@@ -11,7 +11,24 @@
<h1>GCC 16 Release Series</h1>
-<p>As of this time no releases of GCC 16 have yet been made.</p>
+<p>April 30, 2026</p>
+
+<p>The GCC developers are pleased to announce the release of GCC 16.1.</p>
+
+<p>This release is a major release, containing new features (as well
+as many other improvements) relative to GCC 15.x.</p>
+
+<h2>Release History</h2>
+
+<dl>
+
+<dt>GCC 16.1</dt>
+<dd>April 30, 2025
+ (<a href="changes.html">changes</a>,
+ <a href="http://gcc.gnu.org/onlinedocs/16.1.0/";>documentation</a>)
+</dd>
+
+</dl>
<h2>References and Acknowledgements</h2>
commit 6de89e0922c10c33021ce000b0ce630a25005b47
Author: Jakub Jelinek <[email protected]>
Date: Thu Apr 30 10:26:28 2026 +0200
Replace onlinedocs with onlinedocs/gcc-16.1.0 .
diff --git a/htdocs/gcc-16/changes.html b/htdocs/gcc-16/changes.html
index 5ee510b7..37d5578b 100644
--- a/htdocs/gcc-16/changes.html
+++ b/htdocs/gcc-16/changes.html
@@ -37,7 +37,7 @@ a work-in-progress.</p>
See <a href="porting_to.html#solaris">the porting notes</a> for more
information.</li>
<li>The so-called "<code>json</code>" format for
- <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-16.1.0/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format";><code>-fdiagnostics-format=</code></a>
has been removed in this release.
Users seeking machine-readable diagnostics from GCC should use
<a href="https://gcc.gnu.org/wiki/SARIF";>SARIF</a>.
@@ -51,22 +51,22 @@ a work-in-progress.</p>
<h3 id="documentation">Documentation</h3>
<ul>
<li>The documentation for
- <a href="https://gcc.gnu.org/onlinedocs/gcc/Invoking-GCC.html";>
+ <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/Invoking-GCC.html";>
GCC Command Options</a> and the
- <a href="https://gcc.gnu.org/onlinedocs/gcc/Option-Index.html";>
+ <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/Option-Index.html";>
option index</a> have been corrected to include many previously
missing options.</li>
<li>The documentation for
- <a href="https://gcc.gnu.org/onlinedocs/gcc/Attributes.html";>
+ <a href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/Attributes.html";>
GCC-specific attributes</a> has been modernized to put more emphasis
on the standard attribute syntax, which GCC accepts in all supported
dialects of C and C++. The material has also been reorganized to be
less repetitive, and there is a new
- <a href="https://gcc.gnu.org/onlinedocs/gcc/Attribute-Index.html";>
+ <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/Attribute-Index.html";>
index</a> for attributes.</li>
<li>Documentation for parameters and option spec files has been moved
from the main GCC manual to the
- <a href="https://gcc.gnu.org/onlinedocs/gccint/";>
+ <a href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gccint/";>
GCC internals manual</a>.
These features are intended for use by GCC developers and those
who need to build custom GCC configurations.</li>
@@ -84,10 +84,10 @@ a work-in-progress.</p>
</p>
<ul>
- <li>The <a
href="https://gcc.gnu.org/onlinedocs/libgomp/Memory-allocation.html";>
+ <li>The <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgomp/Memory-allocation.html";>
memory allocation</a> support has been enhanced: for allocators with the
<code>pinned</code> trait, including
<code>ompx_gnu_pinned_mem_alloc</code>,
- the <a href="https://gcc.gnu.org/onlinedocs/libgomp/nvptx.html";>CUDA
+ the <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgomp/nvptx.html";>CUDA
API (if available)</a> is used; this improves the performance when
accessing
this memory on Nvidia GPUs. The newly added
<code>ompx_gnu_managed_mem_alloc
</code>allocator and the <code>ompx_gnu_managed_mem_space</code> (both
GNU
@@ -105,9 +105,9 @@ a work-in-progress.</p>
<li>OpenMP 5.2: The <code>begin declare variant</code> directive for C
and C++ is now supported.</li>
<li>OpenMP 6.0: The <a
-
href="https://gcc.gnu.org/onlinedocs/libgomp/omp_005ftarget_005fmemset.html";>
+
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgomp/omp_005ftarget_005fmemset.html";>
<code>omp_target_memset</code></a> and <a
-
href="https://gcc.gnu.org/onlinedocs/libgomp/omp_005ftarget_005fmemset_005fasync.html";>
+
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgomp/omp_005ftarget_005fmemset_005fasync.html";>
<code>omp_target_memset_async</code></a> API routines have been
added. The <code>no_openmp_constructs</code> assumptions clause can now
be used.</li>
@@ -129,15 +129,15 @@ for general information.</p>
<ul>
<li>The <a
-
href="https://gcc.gnu.org/onlinedocs/libgomp/acc_005fmemcpy_005fdevice.html";>
+
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgomp/acc_005fmemcpy_005fdevice.html";>
<code>acc_memcpy_device</code> and
<code>acc_memcpy_device_async</code></a>
API routines have been added for C, C++ and Fortran.</li>
<li>OpenACC 3.0: The <code>wait</code> directive now accepts the
<code>if</code> clause.</li>
<li>OpenACC 3.3: The Fortran API routines <code><a
- href="https://gcc.gnu.org/onlinedocs/libgomp/acc_005fattach.html";>
+
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgomp/acc_005fattach.html";>
acc_attach</a></code> and <code><a
- href="https://gcc.gnu.org/onlinedocs/libgomp/acc_005fdetach.html";>
+
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgomp/acc_005fdetach.html";>
acc_detach</a></code> now augment their OpenACC 2.6 C/C++ counterparts.
</li>
<li>OpenACC 3.4: In Fortran, named constants (<code>PARAMETER</code>) used as
@@ -152,19 +152,19 @@ for general information.</p>
<ul>
<li>
The <a
href="https://github.com/AdaCore/ada-spark-rfcs/blob/master/features/rfc-oop-constructors.rst";>Constructor</a>
<a
href="https://github.com/AdaCore/ada-spark-rfcs/blob/master/features/rfc-oop-constructors.rst";>[RFC]</a>
- and <a
href="https://gcc.gnu.org/onlinedocs/gnat_rm/Destructors.html";>Destructor</a>
<a
href="https://github.com/AdaCore/ada-spark-rfcs/blob/master/features/rfc-oop-destructors.rst";>[RFC]</a>
+ and <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gnat_rm/Destructors.html";>Destructor</a>
<a
href="https://github.com/AdaCore/ada-spark-rfcs/blob/master/features/rfc-oop-destructors.rst";>[RFC]</a>
extensions add new construction/finalization mechanisms that differ
significantly from standard Ada. Those features are inspired by
object-oriented programming in other widely used languages (such as C++).
</li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/gnat_rm/Implicit-With.html";>Implicit
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gnat_rm/Implicit-With.html";>Implicit
with</a> allows a stand-alone use clause in the context clause of a
compilation unit to imply an implicit with of the same library unit where
an equivalent with clause would be allowed.
</li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/gnat_rm/Structural-Generic-Instantiation.html";>Structural
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gnat_rm/Structural-Generic-Instantiation.html";>Structural
Generic
instantiation</a> <a
href="https://github.com/AdaCore/ada-spark-rfcs/blob/master/features/rfc-partial-generic-instantiations.md";>[RFC]</a>
allows reference to an implicit instance of a generic unit, that is
@@ -172,13 +172,13 @@ for general information.</p>
a separately declared name.
</li>
<li>
- The <a
href="https://gcc.gnu.org/onlinedocs/gnat_rm/Aspect-Extended_005fAccess.html";>Extended_Access</a>
+ The <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gnat_rm/Aspect-Extended_005fAccess.html";>Extended_Access</a>
aspect can be specified on a general access type declaration designating an
unconstrained array subtype. It changes the pointer representation and
allows easier interfacing with foreign languages when memory for the
designated object is not allocated by Ada. In particular, it allows the
creation
- of <a
href="https://gcc.gnu.org/onlinedocs/gnat_rm/Aspect-Extended_005fAccess.html";>access
+ of <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gnat_rm/Aspect-Extended_005fAccess.html";>access
to an array
slice</a> <a
href="https://github.com/AdaCore/ada-spark-rfcs/blob/master/features/array_slice_access.md";>[RFC]</a>.
@@ -210,15 +210,15 @@ for general information.</p>
<ul>
<li>C++20 by default: GCC 16 changes the default language version
for C++ compilation from
- <a
href="https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html#index-std-1";>-std=gnu++17</a>
+ <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/C-Dialect-Options.html#index-std-1";>-std=gnu++17</a>
to
- <a
href="https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html#index-std-1";>-std=gnu++20</a>.
+ <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/C-Dialect-Options.html#index-std-1";>-std=gnu++20</a>.
If your code relies on older versions of the C++ standard, you will need to
either add
- <a
href="https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html#index-std-1";>-std=</a>
+ <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/C-Dialect-Options.html#index-std-1";>-std=</a>
to your build flags, or port your code; see <a
href="porting_to.html#cpp">the porting notes</a>.
N.B. C++20 modules support is still experimental and must be enabled by
- <a
href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-fmodules";>-fmodules</a>.
+ <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/C_002b_002b-Dialect-Options.html#index-fmodules";>-fmodules</a>.
</li>
<li>Several C++26 features have been implemented:
<ul>
@@ -274,9 +274,9 @@ for general information.</p>
<li>Various C++ error messages (such as for problems involving templates)
now have a hierarchical structure. This nesting of messages is presented
using indentation and bullet points. The old behavior can be restored via
- <a
href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fno-diagnostics-show-nesting";><code>-fno-diagnostics-show-nesting</code></a>
+ <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/Diagnostic-Message-Formatting-Options.html#index-fno-diagnostics-show-nesting";><code>-fno-diagnostics-show-nesting</code></a>
or
- <a
href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-plain-output";><code>-fdiagnostics-plain-output</code></a>.
+ <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-plain-output";><code>-fdiagnostics-plain-output</code></a>.
<!-- commit d3fe5a560f0bcca8e11ec0f9bb916f59615f51d8
diagnostics: enable nested diagnostics by default [PR116253] -->
<!-- commit 41f071a64ff7027a98e6b6a7e3641156e3be70e0
@@ -319,7 +319,7 @@ for general information.</p>
<ul>
<li>
For targets that support
- <a href="https://gcc.gnu.org/onlinedocs/gcc/_005f_005fint128.html";>128-bit
+ <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/_005f_005fint128.html";>128-bit
integers</a>, <code>std::is_integral<__int128></code> and similar
traits are always true. Previously this was only the case when compiling
with GNU dialects (<code>-std=gnu++17</code>, <code>-std=gnu++14</code>,
@@ -606,7 +606,7 @@ struct Affected : E
<li>Bit-precise integer types (<code>_BitInt (<i>N</i>)</code> and
<code>unsigned _BitInt (<i>N</i>)</code>) are supported.
</li>
- <li>Added FunctionMulti-Versioning (FMV) support. The <a
href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Attributes.html#index-target_005fclones_002c-LoongArch";><code>target_clones</code></a>
+ <li>Added FunctionMulti-Versioning (FMV) support. The <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/LoongArch-Attributes.html#index-target_005fclones_002c-LoongArch";><code>target_clones</code></a>
attribute can be used to generate multiple function versions for
different LoongArch CPU features
(e.g., <code>lsx</code>, <code>lasx</code>), with automatic
@@ -707,11 +707,11 @@ struct Affected : E
<h2 id="diagnostics">Improvements to GCC Diagnostics</h2>
<ul>
<li>GCC can now output diagnostics in HTML form via
- <a
href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-add-output_003dexperimental-html";><code>-fdiagnostics-add-output=experimental-html</code></a>
+ <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-add-output_003dexperimental-html";><code>-fdiagnostics-add-output=experimental-html</code></a>
</li>
<li>GCC's SARIF output now respects the
- <a
href="https://gcc.gnu.org/onlinedocs/gcc/Overall-Options.html#index-dumpdir";>dump
directory</a>.
+ <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/Overall-Options.html#index-dumpdir";>dump
directory</a>.
For example, given
<pre><code>
gcc \
@@ -768,14 +768,14 @@ struct Affected : E
SARIF input.</li>
<li>If
- <a
href="https://gcc.gnu.org/onlinedocs/gcc/Environment-Variables.html#index-GCC_005fDIAGNOSTICS_005fLOG";><code>GCC_DIAGNOSTICS_LOG</code></a>
+ <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/Environment-Variables.html#index-GCC_005fDIAGNOSTICS_005fLOG";><code>GCC_DIAGNOSTICS_LOG</code></a>
is set in the environment, GCC's diagnostic subsystem will emit a
text log to stderr (or a named file) to track what it's doing and the
decisions it's making (e.g. exactly when and why a diagnostic is being
rejected).</li>
<li>If
- <a
href=https://gcc.gnu.org/onlinedocs/gcc/Environment-Variables.html#index-EXPERIMENTAL_005fSARIF_005fSOCKET><code>EXPERIMENTAL_SARIF_SOCKET</code></a>
+ <a
href=https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/Environment-Variables.html#index-EXPERIMENTAL_005fSARIF_005fSOCKET><code>EXPERIMENTAL_SARIF_SOCKET</code></a>
is set in the environment, GCC will attempt to connect to that socket on
startup and send JSON-RPC notifications to it for every diagnostic emitted.
<!-- commit 8a155c170b443e332b3db4922f0f0d588a17604f
@@ -842,7 +842,7 @@ struct Affected : E
assumes that a call to an external function not marked with attribute
<code>nothrow</code> could throw an exception if <code>-fexceptions</code>
is enabled. GCC 16 adds a new option
- <a
href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-fanalyzer-assume-nothrow";><code>-fanalyzer-assume-nothrow</code></a>,
+ <a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/Static-Analyzer-Options.html#index-fanalyzer-assume-nothrow";><code>-fanalyzer-assume-nothrow</code></a>,
for disabling this assumption. This is intended as a workaround for
projects where the exception-handling generates large numbers of new
warnings, such as C code where <code>-fexceptions</code> is used for
@@ -878,57 +878,57 @@ struct Affected : E
<ul>
<li>5 new entrypoints for working with logical locations
<ul>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/logical-locations.html#c.diagnostic_logical_location_get_kind";><code>diagnostic_logical_location_get_kind()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/logical-locations.html#c.diagnostic_logical_location_get_parent";
title="diagnostic_logical_location_get_parent"><code>diagnostic_logical_location_get_parent()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/logical-locations.html#c.diagnostic_logical_location_get_short_name";
title="diagnostic_logical_location_get_short_name"><code>diagnostic_logical_location_get_short_name()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/logical-locations.html#c.diagnostic_logical_location_get_fully_qualified_name";
title="diagnostic_logical_location_get_fully_qualified_name"><code>diagnostic_logical_location_get_fully_qualified_name()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/logical-locations.html#c.diagnostic_logical_location_get_decorated_name";
title="diagnostic_logical_location_get_decorated_name"><code>diagnostic_logical_location_get_decorated_name()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/logical-locations.html#c.diagnostic_logical_location_get_kind";><code>diagnostic_logical_location_get_kind()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/logical-locations.html#c.diagnostic_logical_location_get_parent";
title="diagnostic_logical_location_get_parent"><code>diagnostic_logical_location_get_parent()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/logical-locations.html#c.diagnostic_logical_location_get_short_name";
title="diagnostic_logical_location_get_short_name"><code>diagnostic_logical_location_get_short_name()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/logical-locations.html#c.diagnostic_logical_location_get_fully_qualified_name";
title="diagnostic_logical_location_get_fully_qualified_name"><code>diagnostic_logical_location_get_fully_qualified_name()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/logical-locations.html#c.diagnostic_logical_location_get_decorated_name";
title="diagnostic_logical_location_get_decorated_name"><code>diagnostic_logical_location_get_decorated_name()</code></a></li>
</ul>
</li>
<li>2 new entrypoints for supporting command-line options and SARIF playback
<ul>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/diagnostic-manager.html#c.diagnostic_manager_add_sink_from_spec";
title="diagnostic_manager_add_sink_from_spec"><code>diagnostic_manager_add_sink_from_spec()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/diagnostic-manager.html#c.diagnostic_manager_set_analysis_target";
title="diagnostic_manager_set_analysis_target"><code>diagnostic_manager_set_analysis_target()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/diagnostic-manager.html#c.diagnostic_manager_add_sink_from_spec";
title="diagnostic_manager_add_sink_from_spec"><code>diagnostic_manager_add_sink_from_spec()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/diagnostic-manager.html#c.diagnostic_manager_set_analysis_target";
title="diagnostic_manager_set_analysis_target"><code>diagnostic_manager_set_analysis_target()</code></a></li>
</ul>
</li>
<li>12 new entrypoints for working with directed graphs:
<ul>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/graphs.html#c.diagnostic_manager_new_graph";
title="diagnostic_manager_new_graph"><code>diagnostic_manager_new_graph()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/graphs.html#c.diagnostic_manager_take_global_graph";
title="diagnostic_manager_take_global_graph"><code>diagnostic_manager_take_global_graph()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/graphs.html#c.diagnostic_take_graph";
title="diagnostic_take_graph"><code>diagnostic_take_graph()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/graphs.html#c.diagnostic_graph_release";
title="diagnostic_graph_release"><code>diagnostic_graph_release()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/graphs.html#c.diagnostic_graph_set_description";
title="diagnostic_graph_set_description"><code>diagnostic_graph_set_description()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/graphs.html#c.diagnostic_graph_add_node";
title="diagnostic_graph_add_node"><code>diagnostic_graph_add_node()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/graphs.html#c.diagnostic_graph_add_edge";
title="diagnostic_graph_add_edge"><code>diagnostic_graph_add_edge()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/graphs.html#c.diagnostic_graph_get_node_by_id";
title="diagnostic_graph_get_node_by_id"><code>diagnostic_graph_get_node_by_id()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/graphs.html#c.diagnostic_graph_get_edge_by_id";
title="diagnostic_graph_get_edge_by_id"><code>diagnostic_graph_get_edge_by_id()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/graphs.html#c.diagnostic_node_set_label";
title="diagnostic_node_set_label"><code>diagnostic_node_set_label()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/graphs.html#c.diagnostic_node_set_location";
title="diagnostic_node_set_location"><code>diagnostic_node_set_location()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/graphs.html#c.diagnostic_node_set_logical_location";
title="diagnostic_node_set_logical_location"><code>diagnostic_node_set_logical_location()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/graphs.html#c.diagnostic_manager_new_graph";
title="diagnostic_manager_new_graph"><code>diagnostic_manager_new_graph()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/graphs.html#c.diagnostic_manager_take_global_graph";
title="diagnostic_manager_take_global_graph"><code>diagnostic_manager_take_global_graph()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/graphs.html#c.diagnostic_take_graph";
title="diagnostic_take_graph"><code>diagnostic_take_graph()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/graphs.html#c.diagnostic_graph_release";
title="diagnostic_graph_release"><code>diagnostic_graph_release()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/graphs.html#c.diagnostic_graph_set_description";
title="diagnostic_graph_set_description"><code>diagnostic_graph_set_description()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/graphs.html#c.diagnostic_graph_add_node";
title="diagnostic_graph_add_node"><code>diagnostic_graph_add_node()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/graphs.html#c.diagnostic_graph_add_edge";
title="diagnostic_graph_add_edge"><code>diagnostic_graph_add_edge()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/graphs.html#c.diagnostic_graph_get_node_by_id";
title="diagnostic_graph_get_node_by_id"><code>diagnostic_graph_get_node_by_id()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/graphs.html#c.diagnostic_graph_get_edge_by_id";
title="diagnostic_graph_get_edge_by_id"><code>diagnostic_graph_get_edge_by_id()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/graphs.html#c.diagnostic_node_set_label";
title="diagnostic_node_set_label"><code>diagnostic_node_set_label()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/graphs.html#c.diagnostic_node_set_location";
title="diagnostic_node_set_location"><code>diagnostic_node_set_location()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/graphs.html#c.diagnostic_node_set_logical_location";
title="diagnostic_node_set_logical_location"><code>diagnostic_node_set_logical_location()</code></a></li>
</ul>
</li>
<li>17 new entrypoints for building up text for a diagnostic via a buffer:
<ul>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_new";
title="diagnostic_message_buffer_new"><code>diagnostic_message_buffer_new()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_release";
title="diagnostic_message_buffer_release"><code>diagnostic_message_buffer_release()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_append_str";
title="diagnostic_message_buffer_append_str"><code>diagnostic_message_buffer_append_str()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_append_text";
title="diagnostic_message_buffer_append_text"><code>diagnostic_message_buffer_append_text()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_append_byte";
title="diagnostic_message_buffer_append_byte"><code>diagnostic_message_buffer_append_byte()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_append_printf";
title="diagnostic_message_buffer_append_printf"><code>diagnostic_message_buffer_append_printf()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_append_event_id";
title="diagnostic_message_buffer_append_event_id"><code>diagnostic_message_buffer_append_event_id()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_begin_url";
title="diagnostic_message_buffer_begin_url"><code>diagnostic_message_buffer_begin_url()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_end_url";
title="diagnostic_message_buffer_end_url"><code>diagnostic_message_buffer_end_url()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_begin_quote";
title="diagnostic_message_buffer_begin_quote"><code>diagnostic_message_buffer_begin_quote()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_end_quote";
title="diagnostic_message_buffer_end_quote"><code>diagnostic_message_buffer_end_quote()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_begin_color";
title="diagnostic_message_buffer_begin_color"><code>diagnostic_message_buffer_begin_color()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_end_color";
title="diagnostic_message_buffer_end_color"><code>diagnostic_message_buffer_end_color()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_dump";
title="diagnostic_message_buffer_dump"><code>diagnostic_message_buffer_dump()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/diagnostics.html#c.diagnostic_finish_via_msg_buf";
title="diagnostic_finish_via_msg_buf"><code>diagnostic_finish_via_msg_buf()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/physical-locations.html#c.diagnostic_add_location_with_label_via_msg_buf";
title="diagnostic_add_location_with_label_via_msg_buf"><code>diagnostic_add_location_with_label_via_msg_buf()</code></a></li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/execution-paths.html#c.diagnostic_execution_path_add_event_via_msg_buf";
title="diagnostic_execution_path_add_event_via_msg_buf"><code>diagnostic_execution_path_add_event_via_msg_buf()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_new";
title="diagnostic_message_buffer_new"><code>diagnostic_message_buffer_new()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_release";
title="diagnostic_message_buffer_release"><code>diagnostic_message_buffer_release()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_append_str";
title="diagnostic_message_buffer_append_str"><code>diagnostic_message_buffer_append_str()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_append_text";
title="diagnostic_message_buffer_append_text"><code>diagnostic_message_buffer_append_text()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_append_byte";
title="diagnostic_message_buffer_append_byte"><code>diagnostic_message_buffer_append_byte()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_append_printf";
title="diagnostic_message_buffer_append_printf"><code>diagnostic_message_buffer_append_printf()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_append_event_id";
title="diagnostic_message_buffer_append_event_id"><code>diagnostic_message_buffer_append_event_id()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_begin_url";
title="diagnostic_message_buffer_begin_url"><code>diagnostic_message_buffer_begin_url()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_end_url";
title="diagnostic_message_buffer_end_url"><code>diagnostic_message_buffer_end_url()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_begin_quote";
title="diagnostic_message_buffer_begin_quote"><code>diagnostic_message_buffer_begin_quote()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_end_quote";
title="diagnostic_message_buffer_end_quote"><code>diagnostic_message_buffer_end_quote()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_begin_color";
title="diagnostic_message_buffer_begin_color"><code>diagnostic_message_buffer_begin_color()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_end_color";
title="diagnostic_message_buffer_end_color"><code>diagnostic_message_buffer_end_color()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/message-buffers.html#c.diagnostic_message_buffer_dump";
title="diagnostic_message_buffer_dump"><code>diagnostic_message_buffer_dump()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/diagnostics.html#c.diagnostic_finish_via_msg_buf";
title="diagnostic_finish_via_msg_buf"><code>diagnostic_finish_via_msg_buf()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/physical-locations.html#c.diagnostic_add_location_with_label_via_msg_buf";
title="diagnostic_add_location_with_label_via_msg_buf"><code>diagnostic_add_location_with_label_via_msg_buf()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/execution-paths.html#c.diagnostic_execution_path_add_event_via_msg_buf";
title="diagnostic_execution_path_add_event_via_msg_buf"><code>diagnostic_execution_path_add_event_via_msg_buf()</code></a></li>
</ul>
</li>
- <li><a
href="https://gcc.gnu.org/onlinedocs/libgdiagnostics/topics/physical-locations.html#c.diagnostic_manager_set_debug_physical_locations";
title="diagnostic_manager_set_debug_physical_locations"><code>diagnostic_manager_set_debug_physical_locations()</code></a></li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/libgdiagnostics/topics/physical-locations.html#c.diagnostic_manager_set_debug_physical_locations";
title="diagnostic_manager_set_debug_physical_locations"><code>diagnostic_manager_set_debug_physical_locations()</code></a></li>
<!--
2025-07-15: Added support for message buffers to libgdiagnostics
(LIBGDIAGNOSTICS_ABI_4)
diff --git a/htdocs/gcc-16/index.html b/htdocs/gcc-16/index.html
index 228e58cd..de308c4b 100644
--- a/htdocs/gcc-16/index.html
+++ b/htdocs/gcc-16/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-16.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-16/porting_to.html b/htdocs/gcc-16/porting_to.html
index 2ab0df6f..749b1f3c 100644
--- a/htdocs/gcc-16/porting_to.html
+++ b/htdocs/gcc-16/porting_to.html
@@ -76,7 +76,7 @@ In order to avoid the warnings, one can either remove newly
diagnosed
variables or parameters which aren't used except in pre/post inc/decrements
or compound assignments, make them used in some way, e.g. just
casting to <code>(void)</code>, or lowering the level of the warning. See
-<a
href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wunused-but-set-variable_003d";>
+<a
href="https://gcc.gnu.org/onlinedocs/gcc-16.1.0/gcc/Warning-Options.html#index-Wunused-but-set-variable_003d";>
<code>-Wunused-but-set-*</code></a> documentation for more details.
</p>
-----------------------------------------------------------------------
Summary of changes:
htdocs/gcc-16/changes.html | 149 ++++++++++++++++++++++--------------------
htdocs/gcc-16/index.html | 21 +++++-
htdocs/gcc-16/porting_to.html | 2 +-
3 files changed, 97 insertions(+), 75 deletions(-)
hooks/post-receive
--
gcc-wwwdocs
