public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98750] does not detect dead code [-Wunreachable-code-break]
Date: Wed, 27 Oct 2021 05:08:11 +0000 [thread overview]
Message-ID: <bug-98750-4-d3tsGE7jV1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98750-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98750
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|does not detect dead code |does not detect dead code
| |[-Wunreachable-code-break]
Blocks| |87403
CC| |egallager at gcc dot gnu.org
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> Basically PR 46476 but for break instead of return.
As mentioned in that bug (bug 46476 comment 10), clang puts them under separate
flags, so I'm having this block the "new-warning" meta-bug
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87403
[Bug 87403] [Meta-bug] Issues that suggest a new warning
next prev parent reply other threads:[~2021-10-27 5:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 18:57 [Bug c++/98750] New: does not detect dead code tiagomacarios at gmail dot com
2021-01-19 19:49 ` [Bug c++/98750] " redi at gcc dot gnu.org
2021-01-20 7:56 ` marxin at gcc dot gnu.org
2021-01-20 20:59 ` tiagomacarios at gmail dot com
2021-01-21 10:18 ` redi at gcc dot gnu.org
2021-08-17 9:05 ` pinskia at gcc dot gnu.org
2021-10-27 5:08 ` egallager at gcc dot gnu.org [this message]
2021-11-24 19:06 ` [Bug c++/98750] does not detect dead code [-Wunreachable-code-break] 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-98750-4-d3tsGE7jV1@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).