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++/52312] New: grokfndecl: valgrind problem
Date: Sun, 19 Feb 2012 18:02:00 -0000 [thread overview]
Message-ID: <bug-52312-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52312
Bug #: 52312
Summary: grokfndecl: valgrind problem
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: dcb314@hotmail.com
I just tried to compile the file
gcc/testsuite/g++.dg/cpp0x/udlit-nounder-neg.C under valgrind on trunk
dated 20120216 on an AMD x86_64 box.
Valgrind said
==11414== Conditional jump or move depends on uninitialised value(s)
==11414== at 0x4C442F: grokfndecl(tree_node*, tree_node*, tree_node*,
tree_node*, tree_node*, int, overload_flags, int, tree_node*, int, int, int,
int, special_function_kind, bool, int, tree_node*, tree_node**, unsigned int)
(decl.c:7394)
==11414== by 0x53949D: grokdeclarator(cp_declarator const*,
cp_decl_specifier_seq const*, decl_context, int, tree_node**) (decl.c:10349)
==11414== by 0x53A575: start_decl(cp_declarator const*,
cp_decl_specifier_seq*, int, tree_node*, tree_node*, tree_node**) (decl.c:4346)
==11414== by 0x617793: cp_parser_init_declarator(cp_parser*,
cp_decl_specifier_seq*, VEC_deferred_access_check_gc*, bool, bool, int, bool*,
tree_node**) (parser.c:15660)
No special flags required.
next reply other threads:[~2012-02-19 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-19 18:02 dcb314 at hotmail dot com [this message]
2012-02-19 19:33 ` [Bug c++/52312] " jakub at gcc dot gnu.org
2012-02-19 19:49 ` jakub at gcc dot gnu.org
2012-02-20 23:37 ` jakub at gcc dot gnu.org
2012-02-20 23:43 ` jakub 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-52312-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: link
Be 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).