From: Jozef Lawrynowicz <jozef.l@mittosystems.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: PR 25562: New binutils testsuite failures
Date: Mon, 30 Mar 2020 13:15:30 +0100 [thread overview]
Message-ID: <20200330131530.1df1291f@jozef-kubuntu> (raw)
In-Reply-To: <87a73yrx5b.fsf@redhat.com>
On Mon, 30 Mar 2020 10:48:32 +0100
Nick Clifton <nickc@redhat.com> wrote:
> Hi Jozef,
>
> I am seeing some new binutils testsuite failures for various different
> targets:
>
> Checking Binutils in: arm-wince-pe ... BIN REGRESSION: objcopy executable (pr25662)
> Checking Binutils in: i686-pc-cygwin ... BIN REGRESSION: objcopy executable (pr25662)
> Checking Binutils in: i686-pc-mingw32 ... BIN REGRESSION: objcopy executable (pr25662)
> Checking Binutils in: mcore-pe ... BIN REGRESSION: objcopy executable (pr25662)
> Checking Binutils in: mips-elf ... BIN REGRESSION: objcopy executable (pr25662)
> Checking Binutils in: mips-sgi-irix6 ... BIN REGRESSION: objcopy executable (pr25662)
> Checking Binutils in: mmix-mmixware ... BIN REGRESSION: objcopy executable (pr25662)
> Checking Binutils in: tx39-elf ... BIN REGRESSION: objcopy executable (pr25662)
> Checking Binutils in: x86_64-pc-cygwin ... BIN REGRESSION: objcopy executable (pr25662)
> Checking Binutils in: x86_64-pc-mingw64 ... BIN REGRESSION: objcopy executable (pr25662)
>
> Would you mind taking a look please ?
Hi Nick,
The test is working as expected, for those targets an objcopy of an executable
is not creating an exact copy of the original file.
Alan Modra has already done a triage of the failures (see this thread
https://sourceware.org/pipermail/binutils/2020-March/110422.html), and has setup
XFAILs for some targets. For the remaining failures I think the maintainers of
those targets need to investigate to see if XFAILs are necessary or if there is
a real bug in the toolchain.
For the PE targets the datestamp in the executable file is not being copied by
objcopy.
For the MIPS targets, objcopy has added the names of output sections to the
string table, where in the linked executable they were not in the string table.
I can file bugzillas for these if you would like.
Thanks,
Jozef
>
> Cheers
> Nick
>
>
next prev parent reply other threads:[~2020-03-30 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 9:48 Nick Clifton
2020-03-30 12:15 ` Jozef Lawrynowicz [this message]
2020-03-30 12:26 ` Nick Clifton
2020-03-30 12:36 ` Jozef Lawrynowicz
2020-03-30 12:45 ` Alan Modra
2020-03-30 14:00 ` Nick Clifton
2020-03-30 15:29 ` Nick Clifton
2020-03-31 0:18 ` Maciej W. Rozycki
2020-08-02 12:53 ` Maciej W. Rozycki
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=20200330131530.1df1291f@jozef-kubuntu \
--to=jozef.l@mittosystems.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
/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).