From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Sebastian Huber <sebastian.huber@embedded-brains.de>,
GCC Patches <gcc-patches@gcc.gnu.org>,
fweimer@redhat.com
Subject: Re: [PATCH v2] gcc-14: Mention that some warnings are now errors
Date: Fri, 3 May 2024 18:06:40 +0200 [thread overview]
Message-ID: <ZjULkOOn6dAXDD7M@tucnak> (raw)
In-Reply-To: <ZjT9dNN-qIXwVK64@zen.kayari.org>
On Fri, May 03, 2024 at 04:06:28PM +0100, Jonathan Wakely wrote:
> 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?
LGTM.
> commit fe5fd75ea5a7a08eee0831cadbdd05689e9408db
> Author: Jonathan Wakely <jwakely@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
Jakub
next prev parent reply other threads:[~2024-05-03 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 6:05 Sebastian Huber
2024-04-24 12:28 ` Sebastian Huber
2024-05-02 14:29 ` Sebastian Huber
2024-05-03 15:06 ` Jonathan Wakely
2024-05-03 16:06 ` Jakub Jelinek [this message]
2024-05-03 17:02 ` Sebastian Huber
2024-05-03 17:52 ` Florian Weimer
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=ZjULkOOn6dAXDD7M@tucnak \
--to=jakub@redhat.com \
--cc=fweimer@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=sebastian.huber@embedded-brains.de \
/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: link
Be 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).