On 08/11/2011 08:57 AM, Richard Guenther wrote:
Any idea why the C++ FE prints that funny setbuf.a::mode instead
of simply setbuf.mode for g++.dg/warn/unit-1.C!?
Because by the time we're printing the FIELD_DECL, we've forgotten that
we're in a COMPONENT_REF context. We could do better, but i
This restores some of the uninitialized warnings for memory and
applies some TLC to the machinery.
Any idea why the C++ FE prints that funny setbuf.a::mode instead
of simply setbuf.mode for g++.dg/warn/unit-1.C!? The latter is
what debug_generic_expr dumps.
Bootstrapped and tested on x86_64-unk