From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [PATCH 0/2] Test fix in gdb.arch/* tests
Date: Thu, 22 Mar 2018 12:57:00 -0000 [thread overview]
Message-ID: <cover.1521722330.git.andrew.burgess@embecosm.com> (raw)
While debugging some other patch I hit a random failure in
gdb.arch/amd64-disp-step-avx.exp. I did manage to track down what was
causing the failure, but in the meantime something has changed / been
updated on my machine, and I can no longer recreate the original
failure.
Still, I think that the "fix" is still reasonable, and worth merging
if the list agrees, this is patch #2 of this series.
Patch #1 was just an associated cleanup that I spotted when preparing
patch #2.
Tested on x86-64 GNU/Linux, and on the buildbot with no regressions.
Thanks,
Andrewxs
---
Andrew Burgess (2):
gdb: Minor cleanup in some gdb.arch/* tests
gdb: Fix testsuite issue in gdb.arch/amd64-disp-step-avx.exp
gdb/testsuite/ChangeLog | 17 +++++++++++++++++
gdb/testsuite/gdb.arch/amd64-disp-step-avx.S | 8 +++++---
gdb/testsuite/gdb.arch/amd64-disp-step-avx.exp | 14 ++++++++------
gdb/testsuite/gdb.arch/amd64-disp-step.exp | 4 +---
gdb/testsuite/gdb.arch/arm-disp-step.exp | 4 +---
gdb/testsuite/gdb.arch/i386-disp-step.exp | 5 ++---
gdb/testsuite/gdb.arch/sparc64-regs.exp | 4 +---
7 files changed, 35 insertions(+), 21 deletions(-)
--
2.14.3
next reply other threads:[~2018-03-22 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 12:57 Andrew Burgess [this message]
2018-03-22 12:57 ` [PATCH 2/2] gdb: Fix testsuite issue in gdb.arch/amd64-disp-step-avx.exp Andrew Burgess
2018-03-22 13:44 ` Pedro Alves
2018-03-22 23:01 ` Andrew Burgess
2018-03-23 10:13 ` Pedro Alves
2018-03-22 12:57 ` [PATCH 1/2] gdb: Minor cleanup in some gdb.arch/* tests Andrew Burgess
2018-03-22 13:51 ` Pedro Alves
2018-03-22 22:59 ` Andrew Burgess
2018-03-23 10:13 ` Pedro Alves
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=cover.1521722330.git.andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@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).