Re: Checking failure building arm-elf

[Jan Hubicka <jh at suse dot cz>]

> >>>>> Jan Hubicka writes:
> 
> Jan> Can you send me a backtrace of what happens?  It is really strange as I
> Jan> think I now check the presence of DECL in all paths into cgraph_node.
> 
> #0  0xd0188154 in exit () from /usr/lib/libc.a(shr.o)
> #1  0x1000b270 in internal_error (
>     msgid=0x1050662c "tree check: expected %s, have %s in %s, at %s:%d")
>     at /gcc/dje/src/gcc/diagnostic.c:1200
> #2  0x1001d4d0 in tree_check_failed (node=0x0, code=BLOCK, file=0x0, 
>     line=1059, function=0x104f26a8 "write_source_name")
>     at /gcc/dje/src/gcc/tree.c:4557
> #3  0x103c8944 in write_source_name (identifier=0x200c3d54)
>     at /gcc/dje/src/gcc/cp/mangle.c:1060
> #4  0x103c73e4 in write_name (decl=0x3029a880, ignore_local_scope=-266058584)
>     at /gcc/dje/src/gcc/cp/mangle.c:725
> #5  0x103c9928 in write_local_name (function=0x3029a180, 
>     local_entity=0x3029a880, entity=0x3029a880)
>     at /gcc/dje/src/gcc/cp/mangle.c:1356
> #6  0x103c7404 in write_name (decl=0x3029a880, ignore_local_scope=-266058584)
>     at /gcc/dje/src/gcc/cp/mangle.c:751
> #7  0x103c6ff8 in write_encoding (decl=0x3029a880)
>     at /gcc/dje/src/gcc/cp/mangle.c:656
> #8  0x103cce68 in mangle_decl_string (decl=0x3029a880)
>     at /gcc/dje/src/gcc/cp/mangle.c:2383
> #9  0x103cd140 in mangle_decl (decl=0x3029a880)
>     at /gcc/dje/src/gcc/cp/mangle.c:2405
> #10 0x1000cda0 in decl_assembler_name (decl=0x3029a880)
>     at /gcc/dje/src/gcc/tree.c:152

This is really weird.  I tought that the assembler name is always
evaulated in expand_call, so this should be safe.  I wonder why it is
not.
I will try to dig into the documentation early tomorrow (I have to leave
in 3 minutes from now)

Thanks for the info and soery for the breakage, hope to fix it tomorrow.
Honza