public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Jan Vrany <jan.vrany@labware.com>
To: gdb-patches@sourceware.org
Cc: Jan Vrany <jan.vrany@labware.com>,
	lsix@lancelotsix.com, brobecker@adacore.com, pedro@palves.net
Subject: [PATCH v3 0/2] ppc: recognize all program traps
Date: Wed,  1 Dec 2021 14:30:03 +0000	[thread overview]
Message-ID: <20211201143005.3690440-1-jan.vrany@labware.com> (raw)
In-Reply-To: <20211124130926.2412617-1-jan.vrany@labware.com>

This new mini-series addresses Joel's and Pedro's comments.

Changes since v2:

  * add reference to PowerPC ISA spec in commit message
  * merged PowerPC trap tests to one file handling
    32bit and 64bit PowerPCs.
  * simplified test logic as suggested by Pedro.
  * explicitly set test program status code 0 in
    powerpc-trap.s and powerpc64-trap.s


Jan Vrany (2):
  ppc: use "trap" ("tw, 31, 0, 0") as breakpoint instruction
  ppc: recognize all program traps

 gdb/rs6000-tdep.c                       | 69 +++++++++++++++++++++++-
 gdb/testsuite/gdb.arch/powerpc-trap.exp | 72 +++++++++++++++++++++++++
 gdb/testsuite/gdb.arch/powerpc-trap.s   | 31 +++++++++++
 gdb/testsuite/gdb.arch/powerpc64-trap.s | 33 ++++++++++++
 4 files changed, 203 insertions(+), 2 deletions(-)
 create mode 100644 gdb/testsuite/gdb.arch/powerpc-trap.exp
 create mode 100644 gdb/testsuite/gdb.arch/powerpc-trap.s
 create mode 100644 gdb/testsuite/gdb.arch/powerpc64-trap.s

-- 
2.30.2


  parent reply	other threads:[~2021-12-01 14:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 15:42 [PATCH 1/2] ppc: use 'trap' ('tw, 31, 0, 0', 0x7fe00008) as breakpoint instruction Jan Vrany
2021-11-23 15:42 ` [PATCH 2/2] ppc: recognize all program traps Jan Vrany
2021-11-24 10:43   ` Lancelot SIX
2021-11-24 10:57     ` Lancelot SIX
2021-11-24 13:09 ` [PATCH v2 0/2] " Jan Vrany
2021-11-24 13:09   ` [PATCH v2 1/2] ppc: use 'trap' ('tw, 31, 0, 0', 0x7fe00008) as breakpoint instruction Jan Vrany
2021-11-27  6:45     ` Joel Brobecker
2021-11-29 11:50       ` Jan Vrany
2021-12-01  9:23         ` Joel Brobecker
2021-11-24 13:09   ` [PATCH v2 2/2] ppc: recognize all program traps Jan Vrany
2021-11-27  6:58     ` Joel Brobecker
2021-11-30 12:17     ` Pedro Alves
2021-12-01 13:52       ` Jan Vrany
2021-12-01 14:30   ` Jan Vrany [this message]
2021-12-01 14:30   ` [PATCH v3 1/2] ppc: use "trap" ("tw, 31, 0, 0") as breakpoint instruction Jan Vrany
2021-12-04 10:16     ` Joel Brobecker
2021-12-01 14:30   ` [PATCH v3 2/2] ppc: recognize all program traps Jan Vrany
2021-12-04 10:18     ` Joel Brobecker
2021-12-07 23:30     ` 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=20211201143005.3690440-1-jan.vrany@labware.com \
    --to=jan.vrany@labware.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lsix@lancelotsix.com \
    --cc=pedro@palves.net \
    /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).