From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: amodra@gmail.com
Cc: binutils@sourceware.org
Subject: Regressions with "bfd_arch_get_compatible"
Date: Sat, 04 Jun 2011 12:16:00 -0000 [thread overview]
Message-ID: <201106041216.p54CGIFp020479@ignucius.se.axis.com> (raw)
In-Reply-To: <20110604040358.GB20933@bubble.grove.modra.org> (message from Alan Modra on Sat, 4 Jun 2011 13:33:58 +0930)
> 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
next prev parent reply other threads:[~2011-06-04 12:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 4:04 bfd_arch_get_compatible Alan Modra
2011-06-04 12:16 ` Hans-Peter Nilsson [this message]
2011-06-04 18:18 ` Regressions with "bfd_arch_get_compatible" H.J. Lu
2011-06-05 0:08 ` Hans-Peter Nilsson
2011-06-04 17:20 ` bfd_arch_get_compatible H.J. Lu
2011-06-04 18:00 ` bfd_arch_get_compatible H.J. Lu
2011-06-06 1:26 ` bfd_arch_get_compatible Alan Modra
2011-06-06 2:13 ` bfd_arch_get_compatible H.J. Lu
2011-06-06 2:24 ` bfd_arch_get_compatible H.J. Lu
2011-06-06 2:39 ` bfd_arch_get_compatible Alan Modra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201106041216.p54CGIFp020479@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).