public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92479] missing warnings for unreachable codes with break (i.e. revive the subset of -Wunreachable-code that fits under clang's -Wunreachable-code-break)
Date: Thu, 20 Jan 2022 18:51:40 +0000 [thread overview]
Message-ID: <bug-92479-4-ZBwHHHrkBn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92479-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92479
--- Comment #13 from David Binderman <dcb314 at hotmail dot com> ---
While there are no occurrences of this problem in the gcc source code,
I count six of them in the current Linux kernel source code (v5.16).
Which is more than I would have thought. So this problem does
occur in practice.
next prev parent reply other threads:[~2022-01-20 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-92479-4@http.gcc.gnu.org/bugzilla/>
2021-11-24 19:06 ` egallager at gcc dot gnu.org
2021-11-24 19:07 ` egallager at gcc dot gnu.org
2021-11-29 14:04 ` rguenth at gcc dot gnu.org
2021-11-29 14:10 ` rguenth at gcc dot gnu.org
2021-11-30 5:20 ` egallager at gcc dot gnu.org
2021-11-30 8:12 ` rguenther at suse dot de
2022-01-20 18:48 ` dcb314 at hotmail dot com
2022-01-20 18:51 ` dcb314 at hotmail dot com [this message]
2022-01-22 21:27 ` egallager at gcc dot gnu.org
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-92479-4-ZBwHHHrkBn@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).