Twiddle the assert. A DW_TAG_type_unit in limbo can happen under normal
circumstances while breaking out comdat types.
Found while running the gdb testsuite.
Committed to branch.
Aldy
commit 1c2137a25b7ffa2ab71fe4d534ab149624c5c841
Author: Aldy Hernandez <al...@redhat.com>
Date: Tue Mar 17 16:50:14 2015 -0700
Allow DW_TAG_type_unit's in limbo. They can happen in late debug
while breaking out comdat types.
diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
index c7345d9..30c6cc6 100644
--- a/gcc/dwarf2out.c
+++ b/gcc/dwarf2out.c
@@ -4943,6 +4943,7 @@ new_die (enum dwarf_tag tag_value, dw_die_ref parent_die,
tree t)
because the limbo list should not persist past LTO
streaming. */
if (tag_value != DW_TAG_compile_unit
+ && tag_value != DW_TAG_type_unit
&& !early_dwarf_dumping
/* Allow nested functions to live in limbo because they will
only temporarily live there, as decls_for_scope will fix
