public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Vrany <jan.vrany@labware.com>
Cc: gdb-patches@sourceware.org, lsix@lancelotsix.com,
	brobecker@adacore.com, pedro@palves.net
Subject: Re: [PATCH v3 1/2] ppc: use "trap" ("tw, 31, 0, 0") as breakpoint instruction
Date: Sat, 4 Dec 2021 14:16:55 +0400	[thread overview]
Message-ID: <YatAF4wCvbvlAo5T@adacore.com> (raw)
In-Reply-To: <20211201143005.3690440-2-jan.vrany@labware.com>

Hi Jan,

On Wed, Dec 01, 2021 at 02:30:04PM +0000, Jan Vrany wrote:
> Power ISA 3.0 B spec [1], sections 3.3.11 "Fixed-Point Trap Instructions"
> and section C.6 "Trap Mnemonics" specify "tw, 31, 0, 0" (encoded as
> 0x7fe00008) as canonical unconditional trap instruction.
> 
> This commit changes the breakpoint instruction used by GDB from
> "tw 12, r2, r2" to unconditional "trap".
> 
> [1]: https://openpowerfoundation.org/?resource_lib=power-isa-version-3-0

Thanks for the additional reference. This looks good to me, and
I think it's can be pushed independently of patch #2.

> ---
>  gdb/rs6000-tdep.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/gdb/rs6000-tdep.c b/gdb/rs6000-tdep.c
> index 87a494e0bb8..43880fa4426 100644
> --- a/gdb/rs6000-tdep.c
> +++ b/gdb/rs6000-tdep.c
> @@ -824,8 +824,8 @@ rs6000_fetch_pointer_argument (struct frame_info *frame, int argi,
>  
>  /* Sequence of bytes for breakpoint instruction.  */
>  
> -constexpr gdb_byte big_breakpoint[] = { 0x7d, 0x82, 0x10, 0x08 };
> -constexpr gdb_byte little_breakpoint[] = { 0x08, 0x10, 0x82, 0x7d };
> +constexpr gdb_byte big_breakpoint[] = { 0x7f, 0xe0, 0x00, 0x08 };
> +constexpr gdb_byte little_breakpoint[] = { 0x08, 0x00, 0xe0, 0x7f };
>  
>  typedef BP_MANIPULATION_ENDIAN (little_breakpoint, big_breakpoint)
>    rs6000_breakpoint;
> -- 
> 2.30.2
> 

-- 
Joel

  reply	other threads:[~2021-12-04 10:16 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) " 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   ` [PATCH v3 0/2] " Jan Vrany
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 [this message]
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=YatAF4wCvbvlAo5T@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.vrany@labware.com \
    --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).