public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nunoplopes at sapo dot pt" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105524] New: -Wmaybe-uninitialized false-positive with switch of enum with more than 2 elements Date: Sun, 08 May 2022 18:17:51 +0000 [thread overview] Message-ID: <bug-105524-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105524 Bug ID: 105524 Summary: -Wmaybe-uninitialized false-positive with switch of enum with more than 2 elements Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nunoplopes at sapo dot pt Target Milestone: --- The following program gets a false-positive when compiled with `-Wall -O3 -fstrict-enums`: // switch to 0 to make false-positive go away #define DEF_C 1 enum foo { A, B #if DEF_C , C #endif }; void g(const char*); void f(foo x) { const char *str; switch (x) { case A: str = "a"; break; case B: str = "b"; break; #if DEF_C case C: str = "c"; break; #endif } g(str); } https://gcc.godbolt.org/z/h1rWqezY3 <source>: In function 'void f(foo)': <source>:19:4: error: 'str' may be used uninitialized [-Werror=maybe-uninitialized] 19 | g(str); | ~^~~~~ <source>:11:15: note: 'str' was declared here 11 | const char *str; | ^~~ cc1plus: all warnings being treated as errors Compiler returned: 1 The error only repros with enums with more than 2 elements.
next reply other threads:[~2022-05-08 18:17 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-08 18:17 nunoplopes at sapo dot pt [this message] 2022-05-08 19:17 ` [Bug c++/105524] " pinskia 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-105524-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).