From: Joseph Myers <joseph@codesourcery.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Jeff Law <jeffreyalaw@gmail.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] c: C2x removal of unprototyped functions
Date: Mon, 5 Sep 2022 19:51:59 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2209051950370.743056@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAFiYyc0XzJDoDms1wVVjAJcCpFkthN2SJqfPYwFJROFhhcPH7Q@mail.gmail.com>
On Fri, 2 Sep 2022, Richard Biener via Gcc-patches wrote:
> To catch these cases with a diagnostic earlier is
> -Wstrict-prototypes -Wold-style-declaration enough to diagnose all cases
> that the new standard will reject?
I think so.
> I suppose -W*-c2x-compat are not the correct vehicle to diagnose these?
It could probably be made to diagnose such cases (it doesn't come
automatically because this change involves changed semantics for syntax
that's valid in both standard versions).
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2022-09-05 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 19:12 Joseph Myers
2022-09-01 21:18 ` Jeff Law
2022-09-02 6:16 ` Richard Biener
2022-09-05 19:51 ` Joseph Myers [this message]
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=alpine.DEB.2.22.394.2209051950370.743056@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=richard.guenther@gmail.com \
/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).