public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Adapt gdb.ada/pkd_arr_elem.exp to accept reordered components
Date: Mon, 11 Dec 2017 05:52:00 -0000 [thread overview]
Message-ID: <a9c135fc7d0c005246849ff6b205fd5090248137@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT a9c135fc7d0c005246849ff6b205fd5090248137 ***
Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: a9c135fc7d0c005246849ff6b205fd5090248137
Adapt gdb.ada/pkd_arr_elem.exp to accept reordered components
Recent versions of GNAT are capable of reordering record components
to make their access for efficient. This patch adapts this test to
accept both cases (reordered or not).
gdb/testsuite/ChangeLog:
* gdb.ada/pkd_arr_elem.exp: Adapt "print test" test to accept
output with components being reordered.
next reply other threads:[~2017-12-11 5:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 5:52 sergiodj+buildbot [this message]
2017-12-11 5:52 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, branch master sergiodj+buildbot
2017-12-11 6:00 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-12-11 6:31 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-12-11 7:42 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-12-11 7:47 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-12-11 8:19 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-12-11 8:26 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-12-11 8:32 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
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=a9c135fc7d0c005246849ff6b205fd5090248137@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--cc=gdb-testers@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).