From: Mark Harmstone <mark@harmstone.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org, Tamar.Christina@arm.com,
nickc@redhat.com, pinskia@gmail.com,
Richard.Earnshaw@foss.arm.com, nightstrike@gmail.com,
wej22007@outlook.com, zac.walker@linaro.org
Subject: Re: [PATCH 2/7] Skip ELF-specific tests when targeting pe-aarch64
Date: Fri, 6 Jan 2023 17:48:48 +0000 [thread overview]
Message-ID: <c80fefcc-e433-11c6-4f65-cc17c56e0a4c@harmstone.com> (raw)
In-Reply-To: <4c1fda53-249e-1877-9bd0-dfef0cd6f108@suse.com>
On 6/1/23 08:11, Jan Beulich wrote:
> On 06.01.2023 02:25, Mark Harmstone wrote:
>> --- a/binutils/testsuite/binutils-all/objcopy.exp
>> +++ b/binutils/testsuite/binutils-all/objcopy.exp
>> @@ -1411,6 +1411,7 @@ proc objcopy_test_without_global_symbol { } {
>> # The AArch64 and ARM targets preserve mapping symbols
>> # in object files, so they will fail this test.
>> setup_xfail aarch64*-*-* arm*-*-*
>> +clear_xfail aarch64*-*-pe* aarch64*-*-mingw*
> This change clearly doesn't fit with the title, and hence would better be
> a separate change.
>
>> --- a/gas/testsuite/gas/aarch64/adr_1.d
>> +++ b/gas/testsuite/gas/aarch64/adr_1.d
>> @@ -1,5 +1,6 @@
>> #as: -mabi=lp64
>> #objdump: -dr
>> +#notarget: *-*-pe* *-*-mingw*
> While it's up to the arch maintainers to judge, to me there's nothing ELF-
> specific in this and similar tests; all you need to do is adjust the
> expectations to also accept the COFF form of the respective relocations.
> That's what we do on x86, for example.
>
>> --- a/gas/testsuite/gas/aarch64/advsimd-mov-bad.d
>> +++ b/gas/testsuite/gas/aarch64/advsimd-mov-bad.d
>> @@ -1,5 +1,6 @@
>> #source: advsimd-mov-bad.s
>> #readelf: -s --wide
>> +#notarget: *-*-pe* *-*-mingw*
> Tests using readelf, otoh, are appropriate to exclude. I wonder though
> whether that wouldn't better be done in a more generic manner.
>
> Jan
Hi Jan,
This patch series has already been approved by Nick. I'm resubmitting it because of a last-minute change that ARM insisted we make.
As I think I said before, I'm indifferent towards the two test patches. I'm including them as a courtesy, because they helped reduce the noise when I was working on the rest of the patches. I'm happy to leave them out if they're at all contentious.
Mark
next prev parent reply other threads:[~2023-01-06 17:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 1:25 [PATCH 1/7] Fix size of external_reloc for pe-aarch64 Mark Harmstone
2023-01-06 1:25 ` [PATCH 2/7] Skip ELF-specific tests when targeting pe-aarch64 Mark Harmstone
2023-01-06 8:11 ` Jan Beulich
2023-01-06 17:48 ` Mark Harmstone [this message]
2023-01-09 7:59 ` Jan Beulich
2023-01-06 1:25 ` [PATCH 3/7] Skip big-obj test for pe-aarch64 Mark Harmstone
2023-01-06 8:12 ` Jan Beulich
2023-01-06 1:25 ` [PATCH 4/7] Add pe-aarch64 relocations Mark Harmstone
2023-01-06 1:25 ` [PATCH 5/7] Add .secrel32 for pe-aarch64 Mark Harmstone
2023-01-06 1:25 ` [PATCH 6/7] Add aarch64-w64-mingw32 target Mark Harmstone
2023-01-06 1:25 ` [PATCH 7/7] gas: Restore tc_pe_dwarf2_emit_offset for pe-aarch64 Mark Harmstone
2023-01-06 9:47 ` [PATCH 1/7] Fix size of external_reloc " Christophe Lyon
2023-01-06 17:51 ` Mark Harmstone
2023-01-09 8:11 ` Jan Beulich
2023-01-09 9:22 ` Christophe Lyon
2023-01-09 18:03 ` Mark Harmstone
2023-01-10 8:58 ` Jan Beulich
2023-01-10 23:32 ` Mark Harmstone
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=c80fefcc-e433-11c6-4f65-cc17c56e0a4c@harmstone.com \
--to=mark@harmstone.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=Tamar.Christina@arm.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=nickc@redhat.com \
--cc=nightstrike@gmail.com \
--cc=pinskia@gmail.com \
--cc=wej22007@outlook.com \
--cc=zac.walker@linaro.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).