public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "avarab at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/105273] New: -Wanalyzer-use-of-uninitialized-value warns on "missing" default for switch when callers can be statically determined Date: Thu, 14 Apr 2022 11:23:15 +0000 [thread overview] Message-ID: <bug-105273-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105273 Bug ID: 105273 Summary: -Wanalyzer-use-of-uninitialized-value warns on "missing" default for switch when callers can be statically determined Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: avarab at gmail dot com Target Milestone: --- Created attachment 52807 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52807&action=edit test case with an enum With GCC 12.0 built from c1ff207af66 (ppc: testsuite: skip pr60203 on no ldbl128, 2022-04-12) I get a warning on the attached test case: gcc -fanalyzer analyze.c analyze.c: In function ‘vreportf’: analyze.c:28:17: warning: use of uninitialized value ‘pfx’ [CWE-457] [-Wanalyzer-use-of-uninitialized-value] 28 | snprintf(buf, sizeof(buf), "%s", pfx); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ‘vreportf’: events 1-6 | | 13 | const char *pfx; | | ^~~ | | | | | (1) region created on stack here | 14 | | 15 | switch (kind) { | | ~~~~~~ | | | | | (2) following ‘default:’ branch... |...... | 25 | if (kind == USAGE_BUG) | | ~ | | | | | (3) ...to here | | (4) following ‘false’ branch (when ‘kind != 1’)... |...... | 28 | snprintf(buf, sizeof(buf), "%s", pfx); | | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | | | | | (5) ...to here | | (6) use of uninitialized value ‘pfx’ here |
next reply other threads:[~2022-04-14 11:23 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-14 11:23 avarab at gmail dot com [this message] 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 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@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).