[Bug c++/52311] New: implicitly_declare_fn: valgrind problem

[dcb314 at hotmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52311

             Bug #: 52311
           Summary: implicitly_declare_fn: 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/lambda/lambda-mangle2.C under valgrind on
trunk dated 20120216 on an AMD x86_64 box.

Valgrind said

==19480== Conditional jump or move depends on uninitialised value(s)
==19480==    at 0x666A2A: implicitly_declare_fn(special_function_kind,
tree_node*, bool) (method.c:1538)
==19480==    by 0x66914A: lazily_declare_fn(special_function_kind, tree_node*)
(method.c:1766)
==19480==    by 0x66FA94: lookup_fnfields_1(tree_node*, tree_node*)
(search.c:1449)
==19480==    by 0x673156: lookup_field_r(tree_node*, void*) (search.c:1479)
==19480==    by 0x66D743:
_Z12dfs_walk_allP9tree_nodePFS0_S0_PvES3_S1_.constprop.7 (search.c:1581)
==19480==    by 0x66F5FB: lookup_member(tree_node*, tree_node*, int, bool, int)
(search.c:1213)

No special flags required.