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 analyzer/105273] -Wanalyzer-use-of-uninitialized-value warns on "missing" default for switch when callers can be statically determined Date: Thu, 14 Apr 2022 17:28:18 +0000 [thread overview] Message-ID: <bug-105273-4-WslF3SUHKJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105273-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105273 Eric Gallager <egallager at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic CC| |egallager at gcc dot gnu.org See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=61864 --- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> --- For more discussion of how "default" branches of switch statements affect diagnostics, see also bug 61864 (although that's just for regular diagnostics, and predates the analyzer)
next prev parent reply other threads:[~2022-04-14 17:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-14 11:23 [Bug analyzer/105273] New: " avarab at gmail dot com 2022-04-14 11:25 ` [Bug analyzer/105273] " avarab at gmail dot com 2022-04-14 11:37 ` avarab at gmail dot com 2022-04-14 17:28 ` egallager at gcc dot gnu.org [this message] 2022-04-14 21:04 ` dmalcolm at gcc dot gnu.org 2023-01-12 20:06 ` dmalcolm at gcc dot gnu.org 2023-01-12 21:05 ` dmalcolm at gcc dot gnu.org 2023-01-13 22:52 ` cvs-commit at gcc dot gnu.org 2023-01-13 22:56 ` dmalcolm at gcc dot gnu.org 2023-03-29 23:36 ` dmalcolm 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-105273-4-WslF3SUHKJ@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: linkBe 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).