From: Christophe Lyon <christophe.lyon@arm.com>
To: binutils@sourceware.org
Subject: Re: [PATCH] [arm] Skip ld/pr23169 test on arm.
Date: Mon, 9 Jan 2023 14:28:52 +0100 [thread overview]
Message-ID: <d086a62b-b75e-fc34-30ff-75af3de5e309@arm.com> (raw)
In-Reply-To: <20230103102251.89478-2-christophe.lyon@arm.com>
ping?
(this solves some of the failures reported by Matthias on the 2.40 branch)
On 1/3/23 11:22, Christophe Lyon via Binutils wrote:
> The test is already skipped on several targets (including AArch64)
> because it's invalid.
>
> * testsuite/ld-ifunc/ifunc.exp: Skip pr23169 on arm.
> ---
> ld/testsuite/ld-ifunc/ifunc.exp | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/ld/testsuite/ld-ifunc/ifunc.exp b/ld/testsuite/ld-ifunc/ifunc.exp
> index 15dcee0d967..edabcc3f744 100644
> --- a/ld/testsuite/ld-ifunc/ifunc.exp
> +++ b/ld/testsuite/ld-ifunc/ifunc.exp
> @@ -735,9 +735,10 @@ run_ld_link_exec_tests [list \
> # in the executable (which is relocated last by ld.so).
> if { [isnative]
> && !([istarget "powerpc-*-*"]
> - || [istarget "aarch64*-*-*"]
> - || [istarget "sparc*-*-*"]
> - || [istarget "riscv*-*-*"]) } {
> + || [istarget "aarch64*-*-*"]
> + || [istarget "arm*-*-*"]
> + || [istarget "sparc*-*-*"]
> + || [istarget "riscv*-*-*"]) } {
> run_ld_link_exec_tests [list \
> [list \
> "Run pr23169a" \
next prev parent reply other threads:[~2023-01-09 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 10:22 [PATCH] [arm] Fix PR18841 ifunc relocation ordering Christophe Lyon
2023-01-03 10:22 ` [PATCH] [arm] Skip ld/pr23169 test on arm Christophe Lyon
2023-01-09 13:28 ` Christophe Lyon [this message]
2023-01-09 15:00 ` Nick Clifton
2023-01-09 13:28 ` [PATCH] [arm] Fix PR18841 ifunc relocation ordering Christophe Lyon
2023-01-09 14:59 ` Nick Clifton
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=d086a62b-b75e-fc34-30ff-75af3de5e309@arm.com \
--to=christophe.lyon@arm.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).