public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/55418] New: Valgrind: Conditional jump or move depends on uninitialised value(s) in implicitly_declare_fn() method.c:1623 Date: Tue, 20 Nov 2012 21:36:00 -0000 [thread overview] Message-ID: <bug-55418-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55418 Bug #: 55418 Summary: Valgrind: Conditional jump or move depends on uninitialised value(s) in implicitly_declare_fn() method.c:1623 Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: markus@trippelsdorf.de Just saw this during a -enable-checking=yes,valgrind build: % /var/tmp/gcc_valgrind/usr/local/bin/g++ -std=gnu++11 -c /home/markus/gcc/libstdc++-v3/src/c++11/functexcept.cc ==1267== Conditional jump or move depends on uninitialised value(s) ==1267== at 0x637C0F: implicitly_declare_fn(special_function_kind, tree_node*, bool, tree_node*, tree_node*) (method.c:1623) ==1267== by 0x6392DF: lazily_declare_fn(special_function_kind, tree_node*) (method.c:1894) ==1267== by 0x63FB74: lookup_fnfields_1(tree_node*, tree_node*) (search.c:1441) ==1267== by 0x63FD3B: lookup_fnfields_slot(tree_node*, tree_node*) (search.c:1471) ==1267== by 0x64367B: lookup_field_r(tree_node*, void*) (search.c:1031) ==1267== by 0x6400CE: dfs_walk_all(tree_node*, tree_node* (*)(tree_node*, void*), tree_node* (*)(tree_node*, void*), void*) (search.c:1572) ==1267== by 0x6402E7: lookup_member(tree_node*, tree_node*, int, bool, int) (search.c:1204) ==1267== by 0x640640: lookup_fnfields(tree_node*, tree_node*, int) (search.c:1295) ==1267== by 0x4DF3B0: build_special_member_call(tree_node*, tree_node*, vec<tree_node*, va_gc, vl_embed>**, tree_node*, int, int) (call.c:7282) ==1267== by 0x4E0693: convert_like_real(conversion*, tree_node*, tree_node*, int, int, bool, bool, int) (call.c:5718) ==1267== by 0x4E1D91: build_over_call(z_candidate*, int, int) (call.c:6867) ==1267== by 0x4DE229: build_new_method_call(tree_node*, tree_node*, vec<tree_node*, va_gc, vl_embed>**, tree_node*, int, tree_node**, int) (call.c:7668) ==1267== Looks like some booleans in implicitly_declare_fn should be initialised.
next reply other threads:[~2012-11-20 21:36 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-20 21:36 markus at trippelsdorf dot de [this message] 2012-11-21 14:09 ` [Bug c++/55418] " markus at trippelsdorf dot de 2012-11-21 15:51 ` hp at gcc dot gnu.org 2012-11-22 10:46 ` paolo.carlini at oracle dot com 2012-11-23 15:35 ` paolo at gcc dot gnu.org 2012-11-23 15:36 ` paolo.carlini at oracle dot com 2012-12-05 11:42 ` paolo.carlini at oracle dot com 2013-07-06 23:15 ` paolo.carlini at oracle 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-55418-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).