Re: bfd_link_hash_traverse

["H.J. Lu" <hjl dot tools at gmail dot com>]

On Mon, Jun 13, 2011 at 6:59 AM, Alan Modra <amodra@gmail.com> wrote:
> On Mon, Jun 13, 2011 at 05:55:14AM -0700, H.J. Lu wrote:
>> On Linux/ia64, I got
>>
>> Executing on host: sh -c {tmpdir/ld2 -m elf64_ia64 ?-o tmpdir/ld3
>> -dynamic-linker /lib/ld-linux-ia64.so.2
>> /usr/lib/gcc/ia64-redhat-linux/4.1.2/../../../crt1.o
>> /usr/lib/gcc/ia64-redhat-linux/4.1.2/../../../crti.o
>> /usr/lib/gcc/ia64-redhat-linux/4.1.2/crtbegin.o --traditional-format
>> ldgram.o ldlex-wrapper.o lexsup.o ldlang.o mri.o ldctor.o ldmain.o
>> plugin.o ldwrite.o ldexp.o ?ldemul.o ldver.o ldmisc.o ldfile.o
>> ldcref.o eelf64_ia64.o ?../bfd/.libs/libbfd.a ../libiberty/libiberty.a
>> ? -ldl -lz -ldl ?-L/usr/lib/gcc/ia64-redhat-linux/4.1.2/../../..
>> --start-group /usr/lib/gcc/ia64-redhat-linux/4.1.2/libgcc.a
>> /usr/lib/gcc/ia64-redhat-linux/4.1.2/libgcc_eh.a
>> /usr/lib/gcc/ia64-redhat-linux/4.1.2/../../../libunwind.a -lc
>> --end-group /usr/lib/gcc/ia64-redhat-linux/4.1.2/crtend.o
>> /usr/lib/gcc/ia64-redhat-linux/4.1.2/../../../crtn.o 2>&1} ?/dev/null
>> ld.tmp (timeout = 300)
>> tmpdir/ld2: can't relax section: File truncated
>> tmpdir/ld2: can't relax section: File truncated
>> FAIL: bootstrap with --traditional-format
>
> Unfortunately I don't have an ia64 system available to debug this.
> Can you help out? ?Possibly there is a miscompilation of ld2? ?How
> does ld2 differ from ld1?

ld2 is linked with --traditional-format.  Does it make a difference?

> ia64 was one of the targets that didn't have any problem with its
> treatment of warning symbols, except for elflink.c
> _bfd_elf_export_symbol looking at h->dynamic before following a
> warning symbol link, and that one is unlikely to trigger in the
> bootstrap tests.. ?The files that did have problems were
>

I will investigate.

Thanks.

-- 
H.J.