public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Jambor <mjambor@suse.cz>
To: Florian Weimer <fweimer@redhat.com>, gcc@gcc.gnu.org
Subject: Re: Update on GCC 14 C type safety changes/warnings as errors
Date: Fri, 05 Jan 2024 17:09:38 +0100	[thread overview]
Message-ID: <ri68r53hid9.fsf@> (raw)
In-Reply-To: <87ttp3tek1.fsf@oldenburg.str.redhat.com>

Hello,

On Thu, Nov 30 2023, Florian Weimer via Gcc wrote:
> The patch series is currently under review:
>
>   [PATCH v3 00/11] : More warnings as errors by default
>   <https://inbox.sourceware.org/gcc-patches/cover.1700473918.git.fweimer@redhat.com/>
>
> Jeff as a global reviewer has delegated review to Marek.
>
> The current series is based on an earlier suggestion to do as much as
> possible in one transition.  The full list of upgraded warnings is:
>
>   -Wimplicit-function-declaration
>   -Wimplicit-int
>   -Wint-conversion
>   -Wreturn-mismatch (new, previously part of -Wreturn-types)
>   -Wdeclaration-missing-parameter-type (new, previously unnamed)
>   -Wincompatible-pointer-types

[...]

>
> Thoughts?
>

First and foremost, thanks a lot for working on this and especially for
starting with the enormous task of dealing with the fallout.

Given you probably have the most experience with it, can you please also
suggest an entry to https://gcc.gnu.org/gcc-14/porting_to.html that
would describe this change?  (I was thinking of proposing something
myself, but I don't really know just how much verbose such an entry
should be.)

Thanks!

Martin

  parent reply	other threads:[~2024-01-05 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 16:02 Florian Weimer
2023-12-01  5:37 ` Sam James
2024-01-05 16:09 ` Martin Jambor [this message]
     [not found] ` <74802.124010511100002467@us-mta-352.us.mimecast.lan>
2024-02-02 17:36   ` 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=ri68r53hid9.fsf@ \
    --to=mjambor@suse.cz \
    --cc=fweimer@redhat.com \
    --cc=gcc@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: 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).