Somewhere in the hurricane of debug-early patches of the past month, we
fixed this and forgot verify it was still an issue.
Types are no longer appearing in limbo in late dwarf, so there is no
reason to special case this.
Tested with the guality.exp framework and the gdb testsuite.
Committed to branch.
Aldy
commit 703f3b342cd2d1aa7ec3af45881e08e5eea6942a
Author: Aldy Hernandez <al...@redhat.com>
Date: Fri Mar 20 10:42:05 2015 -0700
Disallow limbo type DIEs in late dwarf generation.
diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
index 48bd5b8..8884afd 100644
--- a/gcc/dwarf2out.c
+++ b/gcc/dwarf2out.c
@@ -4950,10 +4950,6 @@ new_die (enum dwarf_tag tag_value, dw_die_ref
parent_die, tree t)
them up. */
&& (TREE_CODE (t) != FUNCTION_DECL
|| !decl_function_context (t))
- /* FIXME: Allow types for now. We are getting some internal
- template types from inlining (building libstdc++).
- Templates need to be looked at. */
- && !TYPE_P (t)
/* FIXME: Allow late limbo DIE creation for LTO, especially
in the ltrans stage, but once we implement LTO dwarf
streaming, we should remove this exception. */