From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, jakub@redhat.com
Subject: [committed] Require single pointer size in pr24823.sh
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <20190719121125.GA4377@delia> (raw)
Hi,
On MIPS we run into:
...
dwz: 1: DWARF pointer size differs between CUs
dwz: 2: DWARF pointer size differs between CUs
dwz: Too few files for multifile optimization
FAIL: testsuite/dwz.tests/pr24823.sh
...
Fix this by requiring a single pointer size for exec varval in pr24823.sh.
Committed to trunk.
Thanks,
- Tom
Require single pointer size in pr24823.sh
2019-07-19 Tom de Vries <tdevries@suse.de>
* testsuite/dwz.tests/pr24823.sh: Require single pointer size.
---
testsuite/dwz.tests/pr24823.sh | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/testsuite/dwz.tests/pr24823.sh b/testsuite/dwz.tests/pr24823.sh
index f6e5f90..8720aec 100644
--- a/testsuite/dwz.tests/pr24823.sh
+++ b/testsuite/dwz.tests/pr24823.sh
@@ -1,5 +1,14 @@
exec=$execs/varval
+pointer_sizes=$(readelf -wi $exec \
+ | grep "Pointer Size:" \
+ | sort -u \
+ | wc -l)
+
+if [ $pointer_sizes -ne 1 ]; then
+ exit 77
+fi
+
cp $exec 1
cp 1 2
reply other threads:[~2019-07-19 12:11 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=20190719121125.GA4377@delia \
--to=tdevries@suse.de \
--cc=dwz@sourceware.org \
--cc=jakub@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).