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 c++/65301] New: gcc can't detect some uninit reads in ctor init lists Date: Tue, 03 Mar 2015 15:55:00 -0000 [thread overview] Message-ID: <bug-65301-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65301 Bug ID: 65301 Summary: gcc can't detect some uninit reads in ctor init lists Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Given the following source code class K { public: K * copy(); }; class FunctionExpr { public: FunctionExpr( const FunctionExpr & ); private: K * args; }; FunctionExpr::FunctionExpr(const FunctionExpr& expr) : args(expr.args ? args->copy() : 0) { } then trunk gcc can't detect the read of uninit memory for args->copy. $ ~/gcc/results/bin/gcc -c -g -O2 -Wall -Wextra -pedantic bug189.cc $ Here is clang doing the right thing: $ ~/llvm/results/bin/clang++ -c -g -O2 -Wall -Wextra -pedantic bug189.cc bug189.cc:18:28: warning: field 'args' is uninitialized when used here [-Wuninitialized] : args(expr.args ? args->copy() : 0) ^ 1 warning generated. $
next reply other threads:[~2015-03-03 15:55 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-03 15:55 dcb314 at hotmail dot com [this message] 2015-03-03 16:28 ` [Bug c++/65301] " redi at gcc dot gnu.org 2015-03-03 16:31 ` redi at gcc dot gnu.org 2015-03-03 17:45 ` manu 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-65301-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).