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

[David Malcolm via Gcc-patches]

---
 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