[committed 0/6] wwwdocs: various gcc-11/changes fixes

[committed 0/6] wwwdocs: various gcc-11/changes fixes

[David Malcolm]

I've taken the liberty of pushing these changes to the website,
having checked that they validate.

Corrections welcome.

Thanks
Dave

[PATCH 1/6] gcc 11: -fanalyzer now supports GCC plugins

[David Malcolm]

---
 htdocs/gcc-11/changes.html | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 7eeffb98..05b182bc 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -519,6 +519,10 @@ a work-in-progress.</p>
     <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html">-fanalyzer</a>
     is enabled.
   </li>
+  <li>The analyzer can now be extended by GCC plugins, allowing for
+    domain-specific path-sensitive warnings.  An example of using a
+    <a href="https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=66dde7bc64b75d4a338266333c9c490b12d49825">GCC plugin to check for misuses of CPython's global interpreter lock</a>
+    can be seen in the test suite</li>
   <li>The analyzer has gained new debugging options
     <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-fdump-analyzer-json">-fdump-analyzer-json</a> and
     <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-fno-analyzer-feasibility">-fno-analyzer-feasibility</a>.
-- 
2.26.2

[PATCH 2/6] gcc 11: libgccjit is no longer 'alpha'

[David Malcolm]

---
 htdocs/gcc-11/changes.html | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 05b182bc..3c18ef18 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -331,6 +331,12 @@ a work-in-progress.</p>
 <!-- .................................................................. -->
 <h2 id="jit">libgccjit</h2>
 <ul>
+  <li>libgccjit was marked as merely "Alpha" quality when
+    <a href="../gcc-5/changes.html#jit">originally added in GCC 5</a>.
+    Given that we have maintained
+    <a href="https://gcc.gnu.org/onlinedocs/jit/topics/compatibility.html">API and ABI compatibility</a>
+    since then and it is in use by various projects, we have removed that
+    caveat.</li>
   <li>libgccjit can now be built for MinGW</li>
   <li>
     The libgccjit API gained 10 new entry points:
-- 
2.26.2

[PATCH 3/6] gcc 11: document new malloc attribute arguments; integrate into analyzer changes

[David Malcolm]

---
 htdocs/gcc-11/changes.html | 45 ++++++++++++++++++++++++++++----------
 1 file changed, 34 insertions(+), 11 deletions(-)

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 3c18ef18..93c421e3 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -168,12 +168,20 @@ a work-in-progress.</p>
 
 <h3 id="c-family">C family</h3>
 <ul>
-  <li>New attribute:
+  <li>New attributes:
     <ul>
         <li>The <code>no_stack_protector</code> attribute has been added to mark functions which should not be instrumented
             with stack protection (<code>-fstack-protector</code>).</li>
+	<li>The existing
+	  <a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-malloc-function-attribute">malloc</a>
+	  attribute has been extended so that it can be used to identify
+	  allocator/deallocator API pairs.  A new
+	  <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#-Wmismatched-dealloc">-Wmismatched-dealloc</a>
+	  warning will complain about incorrect calls.  Additionally, the
+	  static analyzer will use these attributes when checking for leaks,
+	  double-frees, use-after-frees, and similar issues.
+	</li>
     </ul>
-  </li>
   <li>New warnings:
     <ul>
       <li><code>-Wsizeof-array-div</code>, enabled by <code>-Wall</code>, warns
@@ -507,15 +515,30 @@ a work-in-progress.</p>
     has been completely rewritten for GCC 11, fixing numerous bugs, and
     allowing for the analyzer to scale to larger C source files.
   </li>
-  <li>As preliminary work towards eventually supporting C++, the
-    <code>malloc</code>/<code>free</code> checking within
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html">-fanalyzer</a>
-    has been generalized to also check <code>new</code>/<code>delete</code>
-    and <code>new[]</code>/<code>delete[]</code>, adding a new
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-mismatching-deallocation">-Wanalyzer-mismatching-deallocation</a>
-    warning.  However, C++ is not yet properly supported by
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html">-fanalyzer</a>
-    (for example, exception-handling is unimplemented).</li>
+  <li>The analysis of allocations and deallocations has been generalized
+    beyond <code>malloc</code> and <code>free</code>.
+    <ul>
+      <li>As preliminary work towards eventually supporting C++, the
+	<code>malloc</code>/<code>free</code> checking will also
+	check <code>new</code>/<code>delete</code>
+	and <code>new[]</code>/<code>delete[]</code>.
+	However, C++ is not yet properly supported by
+	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html">-fanalyzer</a>
+	(for example, exception-handling is unimplemented).
+      </li>
+      <li>As noted above, the existing
+	<a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-malloc-function-attribute">malloc</a>
+	attribute has been extended so that it can be used to identify
+	allocator/deallocator API pairs.  The analyzer will use these
+	attributes when checking for leaks, double-frees, use-after-frees, and
+	similar issues.
+      </li>
+      <li>A new
+	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-mismatching-deallocation">-Wanalyzer-mismatching-deallocation</a>
+	warning has been added, covering such mismatches as using
+	scalar <code>delete</code> rather vector <code>delete[]</code>.
+    </ul>
+  </li>
   <li>The analyzer has gained warnings
     <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-shift-count-negative">-Wanalyzer-shift-count-negative</a>,
     <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-shift-count-overflow">-Wanalyzer-shift-count-overflow</a>,
-- 
2.26.2

[PATCH 4/6] gcc 11: document GCC_EXTRA_DIAGNOSTIC_OUTPUT

[David Malcolm]

---
 htdocs/gcc-11/changes.html | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 93c421e3..67e29619 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -562,8 +562,16 @@ a work-in-progress.</p>
 <!-- <h2 id="plugins">Improvements for plugin authors</h2> -->
 
 <!-- .................................................................. -->
-<!-- <h2>Other significant improvements</h2> -->
 
+<h2>Other significant improvements</h2>
+
+<ul>
+  <li>GCC has gained a new environment variable
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Environment-Variables.html#index-GCC_005fEXTRA_005fDIAGNOSTIC_005fOUTPUT">GCC_EXTRA_DIAGNOSTIC_OUTPUT</a>
+    which can be used by IDEs to request machine-readable fix-it hints
+    without needing to adjust build flags.
+  </li>
+</ul>
 
 <!-- .................................................................. -->
 <!-- <h2><a id="GCC11.1">GCC 11.1</a></h2> -->
-- 
2.26.2

[PATCH 5/6] gcc 11: add <code> within <a> where appropriate

[David Malcolm]

---
 htdocs/gcc-11/changes.html | 36 ++++++++++++++++++------------------
 1 file changed, 18 insertions(+), 18 deletions(-)

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 67e29619..ba09587d 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -97,13 +97,13 @@ a work-in-progress.</p>
       In GCC 11 the column numbers default to being column numbers, respecting
       multi-column characters.  The old behavior can be restored using a new
       option
-      <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-column-unit">-fdiagnostics-column-unit=byte</a>.
+      <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-column-unit"><code>-fdiagnostics-column-unit=byte</code></a>.
       There is also a new option
-      <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-column-origin">-fdiagnostics-column-origin=</a>,
+      <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-column-origin"><code>-fdiagnostics-column-origin=</code></a>,
       allowing the pre-existing default of the left-hand column being column
       1 to be overridden if desired (e.g. for 0-based columns).  The output
       of
-      <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format">-fdiagnostics-format=json</a>
+      <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format"><code>-fdiagnostics-format=json</code></a>
       has been extended to supply both byte counts and column numbers for all source locations.
     </p>
     <p>
@@ -112,7 +112,7 @@ a work-in-progress.</p>
       with whitespace or line number information, leading to misalignments
       in the resulting output when compared with the actual source.  Tab
       characters are now printed as an appropriate number of spaces, using the
-      <a href="https://gcc.gnu.org/onlinedocs/gcc/Preprocessor-Options.html#index-ftabstop">-ftabstop</a>
+      <a href="https://gcc.gnu.org/onlinedocs/gcc/Preprocessor-Options.html#index-ftabstop"><code>-ftabstop</code></a>
       option (which defaults to 8 spaces per tab stop).
     </p>
   </li>
@@ -173,10 +173,10 @@ a work-in-progress.</p>
         <li>The <code>no_stack_protector</code> attribute has been added to mark functions which should not be instrumented
             with stack protection (<code>-fstack-protector</code>).</li>
 	<li>The existing
-	  <a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-malloc-function-attribute">malloc</a>
+	  <a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-malloc-function-attribute"><code>malloc</code></a>
 	  attribute has been extended so that it can be used to identify
 	  allocator/deallocator API pairs.  A new
-	  <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#-Wmismatched-dealloc">-Wmismatched-dealloc</a>
+	  <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#-Wmismatched-dealloc"><code>-Wmismatched-dealloc</code></a>
 	  warning will complain about incorrect calls.  Additionally, the
 	  static analyzer will use these attributes when checking for leaks,
 	  double-frees, use-after-frees, and similar issues.
@@ -350,7 +350,7 @@ a work-in-progress.</p>
     The libgccjit API gained 10 new entry points:
     <ul>
       <li>
-	<a href="https://gcc.gnu.org/onlinedocs/jit/topics/expressions.html#c.gcc_jit_global_set_initializer">gcc_jit_global_set_initializer</a>
+	<a href="https://gcc.gnu.org/onlinedocs/jit/topics/expressions.html#c.gcc_jit_global_set_initializer"><code>gcc_jit_global_set_initializer</code></a>
       </li>
       <li>9 entrypoints for <a href="https://gcc.gnu.org/onlinedocs/jit/topics/asm.html">directly embedding asm statements into a compile</a>, analogous to inline <code>asm</code> in the C front end</li>
     </ul>
@@ -523,29 +523,29 @@ a work-in-progress.</p>
 	check <code>new</code>/<code>delete</code>
 	and <code>new[]</code>/<code>delete[]</code>.
 	However, C++ is not yet properly supported by
-	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html">-fanalyzer</a>
+	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html"><code>-fanalyzer</code></a>
 	(for example, exception-handling is unimplemented).
       </li>
       <li>As noted above, the existing
-	<a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-malloc-function-attribute">malloc</a>
+	<a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-malloc-function-attribute"><code>malloc</code></a>
 	attribute has been extended so that it can be used to identify
 	allocator/deallocator API pairs.  The analyzer will use these
 	attributes when checking for leaks, double-frees, use-after-frees, and
 	similar issues.
       </li>
       <li>A new
-	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-mismatching-deallocation">-Wanalyzer-mismatching-deallocation</a>
+	<a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-mismatching-deallocation"><code>-Wanalyzer-mismatching-deallocation</code></a>
 	warning has been added, covering such mismatches as using
 	scalar <code>delete</code> rather vector <code>delete[]</code>.
     </ul>
   </li>
   <li>The analyzer has gained warnings
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-shift-count-negative">-Wanalyzer-shift-count-negative</a>,
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-shift-count-overflow">-Wanalyzer-shift-count-overflow</a>,
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-write-to-const">-Wanalyzer-write-to-const</a>, and
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-write-to-string-literal">-Wanalyzer-write-to-string-literal</a>,
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-shift-count-negative"><code>-Wanalyzer-shift-count-negative</code></a>,
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-shift-count-overflow"><code>-Wanalyzer-shift-count-overflow</code></a>,
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-write-to-const"><code>-Wanalyzer-write-to-const</code></a>, and
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-write-to-string-literal"><code>-Wanalyzer-write-to-string-literal</code></a>,
     all enabled by default when
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html">-fanalyzer</a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html"><code>-fanalyzer</code></a>
     is enabled.
   </li>
   <li>The analyzer can now be extended by GCC plugins, allowing for
@@ -553,8 +553,8 @@ a work-in-progress.</p>
     <a href="https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=66dde7bc64b75d4a338266333c9c490b12d49825">GCC plugin to check for misuses of CPython's global interpreter lock</a>
     can be seen in the test suite</li>
   <li>The analyzer has gained new debugging options
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-fdump-analyzer-json">-fdump-analyzer-json</a> and
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-fno-analyzer-feasibility">-fno-analyzer-feasibility</a>.
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-fdump-analyzer-json"><code>-fdump-analyzer-json</code></a> and
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-fno-analyzer-feasibility"><code>-fno-analyzer-feasibility</code></a>.
   </li>
 </ul>
 
@@ -567,7 +567,7 @@ a work-in-progress.</p>
 
 <ul>
   <li>GCC has gained a new environment variable
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Environment-Variables.html#index-GCC_005fEXTRA_005fDIAGNOSTIC_005fOUTPUT">GCC_EXTRA_DIAGNOSTIC_OUTPUT</a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Environment-Variables.html#index-GCC_005fEXTRA_005fDIAGNOSTIC_005fOUTPUT"><code>GCC_EXTRA_DIAGNOSTIC_OUTPUT</code></a>
     which can be used by IDEs to request machine-readable fix-it hints
     without needing to adjust build flags.
   </li>
-- 
2.26.2

[PATCH 6/6] gcc 11: add documentation link for -Wsizeof-array-div

[David Malcolm]

---
 htdocs/gcc-11/changes.html | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index ba09587d..08a4c93a 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -184,7 +184,8 @@ a work-in-progress.</p>
     </ul>
   <li>New warnings:
     <ul>
-      <li><code>-Wsizeof-array-div</code>, enabled by <code>-Wall</code>, warns
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wsizeof-array-div"><code>-Wsizeof-array-div</code></a>,
+	  enabled by <code>-Wall</code>, warns
 	  about divisions of two sizeof operators when the first one is applied
 	  to an array and the divisor does not equal the size of the array
 	  element.
-- 
2.26.2