GCC mainline failures with ld testsuite
Andreas Schwab
schwab@suse.de
Sat Mar 9 08:34:00 GMT 2002
Andreas Jaeger <aj@suse.de> writes:
|> Since GCC mainline now places zero initialized data in .bss instead
|> .data, some of the elfweak tests fail on i686-linux if you use GCC
|> mainline for compilation:
|>
|> Running /cvs/binutils-mainline/src/ld/testsuite/ld-elfweak/elfweak.exp ...
|> FAIL: ELF DSO weak data first
|> FAIL: ELF DSO weak data last
|> FAIL: ELF weak data first
|> FAIL: ELF weak data last
|>
|> >From the log file:
|> builds/sourceware-src/build-binutils-ln/ld/ld-new -m elf_i386 -o tmpdir/libfoo
|> .so -dynamic-linker /lib/ld-linux.so.2 /usr/lib/crt1.o /usr/lib/crti.o /opt/gcc/
|> 3.2-devel/lib/gcc-lib/i686-pc-linux-gnu/3.2/crtbegin.o --shared tmpdir/foo1a.o
|> tmpdir/bar1a.o /opt/gcc/3.2-devel/lib/gcc-lib/i686-pc-linux-gnu/3.2/libgcc.a -L
|> /usr/lib -lc /opt/gcc/3.2-devel/lib/gcc-lib/i686-pc-linux-gnu/3.2/libgcc.a /opt/
|> gcc/3.2-devel/lib/gcc-lib/i686-pc-linux-gnu/3.2/crtend.o /usr/lib/crtn.o
|> /builds/sourceware-src/build-binutils-ln/ld/../binutils/objdump --dynamic-syms t
|> mpdir/libfoo.so | grep foo$ > tmpdir/objdump.out
|> tmpdir/objdump.out: 0: 00001c8c g DO .bss 00000004 Base de
|> allocate_foo
|> FAIL: ELF DSO weak data last
|>
|> How can we fix the test properly without changing its semantics?
How about matching both .bss and .data, or initializing it with non-zero?
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
More information about the Binutils
mailing list