public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 4f1583a7659e8800f1e240e8b90cc4bcd26f0130 Date: Tue, 27 Apr 2021 08:24:37 +0000 (GMT) [thread overview] Message-ID: <20210427082437.C1041385802A@sourceware.org> (raw) 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 4f1583a7659e8800f1e240e8b90cc4bcd26f0130 (commit) via ccdf40e80d91855985a0b9e344bdb85f5e19346e (commit) from 0c2a938828f1daa5aa2c383e13527ea71712b382 (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 4f1583a7659e8800f1e240e8b90cc4bcd26f0130 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Apr 27 10:22:51 2021 +0200 Releasing 11.1. diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index 3f98df34..5090ec43 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/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 11 has not been released yet, so this document is -a work-in-progress.</p> - <!-- .................................................................. --> <h2>Caveats</h2> <ul> @@ -888,7 +885,15 @@ is built as FAT libraries containing both 32 bit and 64 bit objects.</li> </ul> <!-- .................................................................. --> -<!-- <h2><a id="GCC11.1">GCC 11.1</a></h2> --> +<h2><a name="11.1">GCC 11.1</a></h2> + +<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=11.0">list +of problem reports (PRs)</a> from GCC's bug tracking system that are +known to be fixed in the 11.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-11/index.html b/htdocs/gcc-11/index.html new file mode 100644 index 00000000..cc64e2b7 --- /dev/null +++ b/htdocs/gcc-11/index.html @@ -0,0 +1,56 @@ +<!DOCTYPE html> +<html lang="en"> + +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> +<title>GCC 11 Release Series</title> +<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css" /> +</head> + +<body> + +<h1>GCC 11 Release Series</h1> + +<p>April 27, 2021</p> + +<p>The GCC developers are pleased to announce the release of GCC 11.1.</p> + +<p>This release is a major release, containing new features (as well +as many other improvements) relative to GCC 10.x.</p> + +<h2>Release History</h2> + +<dl> + +<dt>GCC 11.1</dt> +<dd>April 27, 2021 + (<a href="changes.html">changes</a>, + <a href="http://gcc.gnu.org/onlinedocs/11.1.0/">documentation</a>) +</dd> + +</dl> + +<h2>References and Acknowledgements</h2> + +<p>GCC used to stand for the GNU C Compiler, but since the compiler +supports several other languages aside from C, it now stands for the +GNU Compiler Collection.</p> + +<p>A list of <a href="buildstat.html">successful builds</a> is updated +as new information becomes available.</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-11.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 +<a href="../index.html">GCC project web site</a> or contact the +<a href="mailto:gcc@gcc.gnu.org">GCC development mailing list</a>.</p> + +<p>To obtain GCC please use <a href="../mirrors.html">our mirror sites</a> +or <a href="../git.html">our version control system</a>.</p> + +</body> +</html> commit ccdf40e80d91855985a0b9e344bdb85f5e19346e Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Apr 27 10:02:30 2021 +0200 Point into 11.1.0 onlinedocs instead of trunk. diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index 7689507e..3f98df34 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -101,13 +101,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"><code>-fdiagnostics-column-unit=byte</code></a>. + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/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"><code>-fdiagnostics-column-origin=</code></a>, + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/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"><code>-fdiagnostics-format=json</code></a> + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/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> @@ -116,7 +116,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"><code>-ftabstop</code></a> + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Preprocessor-Options.html#index-ftabstop"><code>-ftabstop</code></a> option (which defaults to 8 spaces per tab stop). </p> </li> @@ -235,7 +235,7 @@ a work-in-progress.</p> Fortran compilers. See the <a href="https://gcc.gnu.org/wiki/OpenACC/Implementation%20Status#status-11">implementation status</a> section on the OpenACC wiki page and the - <a href="https://gcc.gnu.org/onlinedocs/libgomp/Enabling-OpenACC.html"> + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/libgomp/Enabling-OpenACC.html"> run-time library documentation</a> for further information. </li> </ul> @@ -248,15 +248,15 @@ a work-in-progress.</p> <ul> <li>New attributes: <ul> - <li>The <a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-no_005fstack_005fprotector-function-attribute"><code>no_stack_protector</code></a> + <li>The <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Common-Function-Attributes.html#index-no_005fstack_005fprotector-function-attribute"><code>no_stack_protector</code></a> 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"><code>malloc</code></a> + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/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 pair of new - <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wmismatched-dealloc"><code>-Wmismatched-dealloc</code></a> and <a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-Wmismatched-new-delete"><code>-Wmismatched-new-delete</code></a> warnings will complain - about mismatched calls, and <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wfree-nonheap-object"><code>-Wfree-nonheap-object</code></a> about deallocation calls with pointers not obtained from allocation + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Warning-Options.html#index-Wmismatched-dealloc"><code>-Wmismatched-dealloc</code></a> and <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/C_002b_002b-Dialect-Options.html#index-Wmismatched-new-delete"><code>-Wmismatched-new-delete</code></a> warnings will complain + about mismatched calls, and <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Warning-Options.html#index-Wfree-nonheap-object"><code>-Wfree-nonheap-object</code></a> about deallocation calls with pointers not obtained from allocation functions. Additionally, the static analyzer will use these attributes when checking for leaks, double-frees, use-after-frees, and similar issues. @@ -264,23 +264,23 @@ a work-in-progress.</p> </ul> <li>New warnings: <ul> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wmismatched-dealloc"><code>-Wmismatched-dealloc</code></a>, + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Warning-Options.html#index-Wmismatched-dealloc"><code>-Wmismatched-dealloc</code></a>, enabled by default, warns about calls to deallocation functions with pointers returned from mismatched allocation functions. </li> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wsizeof-array-div"><code>-Wsizeof-array-div</code></a>, + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/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. </li> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wstringop-overread"><code>-Wstringop-overread</code></a>, + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Warning-Options.html#index-Wstringop-overread"><code>-Wstringop-overread</code></a>, enabled by default, warns about calls to string functions reading past the end of the arrays passed to them as arguments. In prior GCC releases most instances of his warning are diagnosed by <code>-Wstringop-overflow</code>. </li> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wtsan"><code>-Wtsan</code></a>, + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Warning-Options.html#index-Wtsan"><code>-Wtsan</code></a>, enabled by default, warns about unsupported features in ThreadSanitizer (currently <code>std::atomic_thread_fence</code>). </li> @@ -288,15 +288,15 @@ a work-in-progress.</p> </li> <li>Enhancements to existing warnings: <ul> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wfree-nonheap-object"><code>-Wfree-nonheap-object</code></a> + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Warning-Options.html#index-Wfree-nonheap-object"><code>-Wfree-nonheap-object</code></a> detects many more instances of calls to deallocation functions with pointers not returned from a dynamic memory allocation function. </li> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wmaybe-uninitialized"><code>-Wmaybe-uninitialized</code></a> + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Warning-Options.html#index-Wmaybe-uninitialized"><code>-Wmaybe-uninitialized</code></a> diagnoses passing pointers or references to uninitialized memory to functions taking <code>const</code>-qualified arguments. </li> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wuninitialized"><code>-Wuninitialized</code></a> + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Warning-Options.html#index-Wuninitialized"><code>-Wuninitialized</code></a> detects reads from uninitialized dynamically allocated memory. </li> </ul> @@ -331,7 +331,7 @@ a work-in-progress.</p> <li> New command-line options: <ul> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html#index-fno-bit-tests"><code>-fbit-tests</code></a>, enabled by default, can be used to enable or disable switch expansion using bit-tests.</li> + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Code-Gen-Options.html#index-fno-bit-tests"><code>-fbit-tests</code></a>, enabled by default, can be used to enable or disable switch expansion using bit-tests.</li> </ul> </li> <li>GCOV data file format outputs smaller files by representing zero counters in a more compact way.</li> @@ -380,13 +380,13 @@ a work-in-progress.</p> </ul></li> <li>New warnings: <ul> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Warray-parameter"><code>-Warray-parameter</code></a>, + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Warning-Options.html#index-Warray-parameter"><code>-Warray-parameter</code></a>, enabled by <code>-Wall</code>, warns about redeclarations of functions with ordinary array arguments declared using inconsistent forms. The warning also enables the detection of the likely out of bounds accesses in calls to such functions with smaller arrays. </li> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wvla-parameter"><code>-Wvla-parameter</code></a>, + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Warning-Options.html#index-Wvla-parameter"><code>-Wvla-parameter</code></a>, enabled by <code>-Wall</code>, warns redeclarations of functions with variable length array arguments declared using inconsistent forms or with mismatched bounds. The warning also enables @@ -453,34 +453,34 @@ a work-in-progress.</p> (<a href="https://gcc.gnu.org/PR97518">PR97518</a>).</li> <li>New warnings: <ul> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-Wctad-maybe-unsupported"><code>-Wctad-maybe-unsupported</code></a>, + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/C_002b_002b-Dialect-Options.html#index-Wctad-maybe-unsupported"><code>-Wctad-maybe-unsupported</code></a>, disabled by default, warns about performing class template argument deduction on a type with no deduction guides. </li> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-Wrange-loop-construct"><code>-Wrange-loop-construct</code></a>, + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/C_002b_002b-Dialect-Options.html#index-Wrange-loop-construct"><code>-Wrange-loop-construct</code></a>, enabled by <code>-Wall</code>, warns when a range-based for-loop is creating unnecessary and expensive copies. </li> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-Wdeprecated-enum-enum-conversion"><code>-Wdeprecated-enum-enum-conversion</code></a>, + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/C_002b_002b-Dialect-Options.html#index-Wdeprecated-enum-enum-conversion"><code>-Wdeprecated-enum-enum-conversion</code></a>, enabled by default in C++20, warns about deprecated arithmetic conversions on operands of enumeration types, as outlined in <em>[depr.arith.conv.enum]</em>. </li> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-Wdeprecated-enum-float-conversion"><code>-Wdeprecated-enum-float-conversion</code></a>, + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/C_002b_002b-Dialect-Options.html#index-Wdeprecated-enum-float-conversion"><code>-Wdeprecated-enum-float-conversion</code></a>, enabled by default in C++20, warns about deprecated arithmetic conversions on operands where one is of enumeration type and the other is of a floating-point type, as outlined in <em>[depr.arith.conv.enum]</em>. </li> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-Wmismatched-new-delete"><code>-Wmismatched-new-delete</code></a>, + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/C_002b_002b-Dialect-Options.html#index-Wmismatched-new-delete"><code>-Wmismatched-new-delete</code></a>, enabled by <code>-Wall</code>, warns about calls to C++ <code>operator delete</code> with pointers returned from mismatched forms of <code>operator new</code> or from other mismatched allocation functions. </li> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-Wvexing-parse"><code>-Wvexing-parse</code></a>, + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/C_002b_002b-Dialect-Options.html#index-Wvexing-parse"><code>-Wvexing-parse</code></a>, enabled by default, warns about the most vexing parse rule: the cases when a declaration looks like a variable definition, but the C++ language requires it to be interpreted as a @@ -489,7 +489,7 @@ a work-in-progress.</p> </ul> <li>Enhancements to existing warnings: <ul> - <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wnonnull"><code>-Wnonnull</code></a> + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Warning-Options.html#index-Wnonnull"><code>-Wnonnull</code></a> considers the implicit <code>this</code> argument of every C++ nonstatic member function to have been implicitly declared with attribute <code>nonnull</code> and triggers warnings for calls where @@ -553,7 +553,7 @@ a work-in-progress.</p> <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> + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/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> @@ -561,9 +561,9 @@ 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"><code>gcc_jit_global_set_initializer</code></a> + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/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> + <li>9 entrypoints for <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/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> </li> </ul> @@ -825,7 +825,7 @@ is built as FAT libraries containing both 32 bit and 64 bit objects.</li> <h2 id="analyzer">Improvements to Static Analyzer</h2> <ul> <li>The implementation of how program state is tracked within - <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html">-fanalyzer</a> + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Static-Analyzer-Options.html">-fanalyzer</a> has been completely rewritten for GCC 11, fixing numerous bugs, and allowing for the analyzer to scale to larger C source files. </li> @@ -837,29 +837,29 @@ is built as FAT libraries containing both 32 bit and 64 bit objects.</li> 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"><code>-fanalyzer</code></a> + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/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"><code>malloc</code></a> + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/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"><code>-Wanalyzer-mismatching-deallocation</code></a> + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/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"><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>, + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/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-11.1.0/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-11.1.0/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-11.1.0/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"><code>-fanalyzer</code></a> + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Static-Analyzer-Options.html"><code>-fanalyzer</code></a> is enabled. </li> <li>The analyzer can now be extended by GCC plugins, allowing for @@ -867,8 +867,8 @@ is built as FAT libraries containing both 32 bit and 64 bit objects.</li> <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"><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>. + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Static-Analyzer-Options.html#index-fdump-analyzer-json"><code>-fdump-analyzer-json</code></a> and + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Static-Analyzer-Options.html#index-fno-analyzer-feasibility"><code>-fno-analyzer-feasibility</code></a>. </li> </ul> @@ -881,7 +881,7 @@ is built as FAT libraries containing both 32 bit and 64 bit objects.</li> <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"><code>GCC_EXTRA_DIAGNOSTIC_OUTPUT</code></a> + <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/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> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 95 ++++++++++++++++++----------------- htdocs/{gcc-4.1 => gcc-11}/index.html | 35 ++++--------- 2 files changed, 61 insertions(+), 69 deletions(-) copy htdocs/{gcc-4.1 => gcc-11}/index.html (60%) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-04-27 8:24 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210427082437.C1041385802A@sourceware.org \ --to=jakub@sourceware.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).