On 02/05/24 16:29 +0200, Sebastian Huber wrote:
On 24.04.24 14:28, Sebastian Huber wrote:
----- Am 15. Apr 2024 um 8:05 schrieb Sebastian Huber
sebastian.hu...@embedded-brains.de:
---
v2: Remove listing of options.
htdocs/gcc-14/changes.html | 2 ++
1 file changed, 2 insertions(+)
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 8ac08e9a..665d050a 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -231,6 +231,8 @@ a work-in-progress.</p>
previous options <code>-std=c2x</code>, <code>-std=gnu2x</code>
and <code>-Wc11-c2x-compat</code>, which are deprecated but remain
supported.</li>
+ <li>Some warnings are now errors by default (see also
+ <a href="porting_to.html">Porting to GCC 14</a>).</li>
</ul>
<h3 id="cxx">C++</h3>
--
2.35.3
Ping.
I think it would be helpful to reference this change in the C section.
This warning to error change causes some issues with legacy software.
I agree it should be mentioned, but I would put it in the caveats
section at the top, not as the last item of the C section.
How about this? OK for wwwdocs?
-- >8 --
commit fe5fd75ea5a7a08eee0831cadbdd05689e9408db
Author: Jonathan Wakely <jwak...@redhat.com>
Date: Fri May 3 16:04:49 2024 +0100
Add caveat to GCC 14 release notes about C warnings-as-errors change
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 46a0266d..82906de1 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -40,6 +40,11 @@ a work-in-progress.</p>
<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
identify all such cases in the source code and modify them.
</li>
+ <li><strong>C:</strong>
+ Certain warnings about are now errors, see
+ <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>
is refactored, to override <code>-fcf-protection</code>,
<code>-fcf-protection=none</code> needs to be added and then
