From: Alan Modra <amodra@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] ld-elf/eh5 remove xfail hppa64
Date: Wed, 7 Jun 2023 09:33:40 +0000 (GMT) [thread overview]
Message-ID: <20230607093340.C49D73858C54@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=c6cad198b15e90df947921b58a0f052635050b4d
commit c6cad198b15e90df947921b58a0f052635050b4d
Author: Alan Modra <amodra@gmail.com>
Date: Wed Jun 7 17:28:22 2023 +0930
ld-elf/eh5 remove xfail hppa64
Commit cb81e84c72 resulted in an xpass for hppa64-hp-hpux11, but the
test still fails on hpp64-linux. Let's make it pass for hppa64-linux
too, by accepting pcrel sdata8 encoding in the augmentation data.
Diff:
---
ld/testsuite/ld-elf/eh5.d | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/ld/testsuite/ld-elf/eh5.d b/ld/testsuite/ld-elf/eh5.d
index 3f3fd2d0354..cec87105915 100644
--- a/ld/testsuite/ld-elf/eh5.d
+++ b/ld/testsuite/ld-elf/eh5.d
@@ -4,7 +4,7 @@
#ld:
#readelf: -wf
#target: [check_as_cfi]
-#xfail: alpha-*-*ecoff hppa64-*-* tile*-*-* visium-*-*
+#xfail: alpha-*-*ecoff tile*-*-* visium-*-*
Contents of the .eh_frame section:
@@ -14,7 +14,7 @@ Contents of the .eh_frame section:
Code alignment factor: .*
Data alignment factor: .*
Return address column: .*
- Augmentation data: (0b|0c|1b)
+ Augmentation data: [01][bc]
DW_CFA_nop
DW_CFA_nop
@@ -37,7 +37,7 @@ Contents of the .eh_frame section:
Code alignment factor: .*
Data alignment factor: .*
Return address column: .*
- Augmentation data: 03 .. .. .. .. (0b|0c|1b)
+ Augmentation data: 03 .. .. .. .. [01][bc]
DW_CFA_nop
@@ -61,7 +61,7 @@ Contents of the .eh_frame section:
Code alignment factor: .*
Data alignment factor: .*
Return address column: .*
- Augmentation data: 03 .. .. .. .. 0c (0b|0c|1b)
+ Augmentation data: 03 .. .. .. .. 0c [01][bc]
DW_CFA_nop
DW_CFA_nop
@@ -86,7 +86,7 @@ Contents of the .eh_frame section:
Code alignment factor: .*
Data alignment factor: .*
Return address column: .*
- Augmentation data: (0b|0c|1b)
+ Augmentation data: [01][bc]
DW_CFA_def_cfa: r0(.*) ofs 16
#? DW_CFA_nop
@@ -109,7 +109,7 @@ Contents of the .eh_frame section:
Code alignment factor: .*
Data alignment factor: .*
Return address column: .*
- Augmentation data: 03 .. .. .. .. (0b|0c|1b)
+ Augmentation data: 03 .. .. .. .. [01][bc]
DW_CFA_nop
#? DW_CFA_nop
@@ -139,7 +139,7 @@ Contents of the .eh_frame section:
Code alignment factor: .*
Data alignment factor: .*
Return address column: .*
- Augmentation data: 03 .. .. .. .. 0c (0b|0c|1b)
+ Augmentation data: 03 .. .. .. .. 0c [01][bc]
DW_CFA_nop
DW_CFA_nop
reply other threads:[~2023-06-07 9:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230607093340.C49D73858C54@sourceware.org \
--to=amodra@sourceware.org \
--cc=bfd-cvs@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).