This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Regressions with "bfd_arch_get_compatible"
- From: Hans-Peter Nilsson <hans-peter dot nilsson at axis dot com>
- To: amodra at gmail dot com
- Cc: binutils at sourceware dot org
- Date: Sat, 4 Jun 2011 14:16:18 +0200
- Subject: Regressions with "bfd_arch_get_compatible"
> Date: Sat, 4 Jun 2011 13:33:58 +0930
> From: Alan Modra <amodra@gmail.com>
> * archures.c (bfd_arch_get_compatible): If one arch is unknown,
> return the other arch.
> * elfcode.h (elf_object_p): Allow explicit match to generic ELF
> target.
Looks like the target lost leverage in bfd_arch_get_compatible.
Regressions for cris-elf:
binutils:
Running /tmp/hpautotest-binutils/bsrc/src/binutils/testsuite/binutils-all/compress.exp ...
FAIL: objcopy (objcopy decompress debug sections in archive)
In binutils.log:
Executing on host: /tmp/hpautotest-binutils/cris-axis-elf/binutils/objcopy --decompress-debug-sections tmpdir/libdw2.a tmpdir/dw2-copy.a (timeout = 300)
/tmp/hpautotest-binutils/cris-axis-elf/binutils/objcopy:tmpdir/libdw2.a(dw2-1-compressed.o): Unable to recognise the format of file: File format is ambiguous
/tmp/hpautotest-binutils/cris-axis-elf/binutils/objcopy:tmpdir/libdw2.a(dw2-1-compressed.o): Unable to recognise the format of file: File format is ambiguous
FAIL: objcopy (objcopy decompress debug sections in archive)
That can only be a universal regression, right?
ld:
Running /tmp/hpautotest-binutils/bsrc/src/ld/testsuite/ld-cris/cris.exp ...
FAIL: ld-cris/badgotr1
In ld.log:
Executing on host: sh -c {./ld-new -L/tmp/hpautotest-binutils/bsrc/src/ld/testsuite/ld-cris -m crislinux -shared -o tmpdir/dump tmpdir/dump0.o 2>&1} /dev/null ld.tmp (timeout = 300)
tmpdir/dump0.o: file not recognized: File format is ambiguous
tmpdir/dump0.o: matching formats: elf32-us-cris elf32-little
failed with: <tmpdir/dump0.o: file not recognized: File format is ambiguous
tmpdir/dump0.o: matching formats: elf32-us-cris elf32-little>, expected: <\A[^\nc][^\n]*o: uses _-prefixed [^\nc]*\n[^\nc][^\n]* failed to merge [^\n]*\n[^\nc][^\n]* no GOT [^\n]*\n[^\nc][^\n]* Bad value\Z>
I'd rather keep the old message, being slightly more user-friendly.
(And the new one implies that, although both choices are wrong,
that one of the listed choices is the right one!)
brgds, H-P