public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/111654] Introduce clang's invalid-noreturn warning
Date: Mon, 02 Oct 2023 09:41:21 +0000 [thread overview]
Message-ID: <bug-111654-4-THLrJjqLa0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111654-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111654
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Julian Waters from comment #0)
> Created attachment 56022 [details]
> Patch to add invalid-noreturn to gcc
Patches should be submitted to gcc-patches@gcc.gnu.org
For more details, please read:
https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps
Except for clang compatibility, I believe the consensus is that numerical
levels are not user-friendly. I think it would be better to have:
-Wnoreturn-implicit-return
-Wnoreturn-explicit-return
-Winvalid-noreturn enables / disables both.
next prev parent reply other threads:[~2023-10-02 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 13:09 [Bug driver/111654] New: " tanksherman27 at gmail dot com
2023-10-02 9:41 ` manu at gcc dot gnu.org [this message]
2023-10-02 10:17 ` [Bug c/111654] " tanksherman27 at gmail dot com
2023-10-02 10:22 ` sjames at gcc dot gnu.org
2023-10-02 12:46 ` manu at gcc dot gnu.org
2023-10-02 23:21 ` egallager at gcc dot gnu.org
2023-10-18 8:12 ` tanksherman27 at gmail dot com
2024-05-26 12:18 ` tanksherman27 at gmail dot com
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=bug-111654-4-THLrJjqLa0@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).