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 target/99674] gcc/config/i386/i386-features.c: 2143: 2 * member variable not inited in ctor ? Date: Fri, 19 Mar 2021 21:16:09 +0000 [thread overview] Message-ID: <bug-99674-4-CeyK6wyRu0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99674-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99674 --- Comment #1 from David Binderman <dcb314 at hotmail dot com> --- A straightforward generalisation of this bug report would be for gcc to warn on code like this: struct S { int a, b, c; S(); }; S::S() : a( 0), c( 2) { }; cppcheck finds the problem but gcc and clang don't. mar19g.cc:11:4: warning: Member variable 'S::b' is not initialized in the constructor. [uninitMemberVar] Interestingly, there are about 125 cases of this in the gcc source code, so this warning would be of immediate use for gcc itself. List available on request.
next prev parent reply other threads:[~2021-03-19 21:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-19 21:04 [Bug target/99674] New: " dcb314 at hotmail dot com 2021-03-19 21:16 ` dcb314 at hotmail dot com [this message] 2022-01-10 20:09 ` [Bug target/99674] " dcb314 at hotmail dot com
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-99674-4-CeyK6wyRu0@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).