public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Carl Love <cel@us.ibm.com>
To: gdb-patches@sourceware.org, Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Cc: Will Schmidt <will_schmidt@vnet.ibm.com>,
	Tulio Magno <tuliom@linux.ibm.com>,
	Rogerio Alves <rogealve@br.ibm.com>,
	cel@us.ibm.com
Subject: [PATCH 0/2] Add recording support for the ISA 3.1 Powerpc instructions
Date: Fri, 04 Mar 2022 11:46:37 -0800	[thread overview]
Message-ID: <7ff0655bead2a8245018fbf9624f207cd38a5b7f.camel@us.ibm.com> (raw)

GDB maintainers:

The gdb record functionality does not have support for the the Powerpc
ISA 3.1 instructions.  

The first patch in this series will add the missing support to record
the registers for each of the ISA 3.1 instructions.

The second patch in the series adds two test cases.  The first test
case verifies the recording works for a few of the ISA 2.06
instructions.  The second case verifies recording of a few ISA 3.1
instructions.

I have used the Valgrind ISA 3.1 testsuite to verify that all of the
ISA 3.1 instructions are recognized by gdb record.  Additionally, I
manually ran gdb stoping at the Valgrind test function for each of the
new instructions.  I then verified that all of the expected registers
changed and were then restored when the instruction was executed in
reverse.  Basically, the test process consisted of stopping at the isa
instruction, issue the gdb command record command, info registers all
saving the output file 1, si,  info registers all saving the output
file 2, reverse-stepi, info registers all saving the output file 3.  I
then diffed files 1 and 2 to verify the test changed all of the
registers specified in the ISA. Finally, diff files 1 and 3 to verify
all of the registers were restored.

                        Carl Love


             reply	other threads:[~2022-03-04 19:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 19:46 Carl Love [this message]
2022-03-04 19:52 ` [PATCH 1/2] " Carl Love
2022-03-06 11:53   ` Joel Brobecker
2022-04-12 17:09     ` [PATCH 1/2 Version 2] " Carl Love
2022-04-12 21:50       ` will schmidt
2022-04-13 17:26         ` [PATCH 1/2 Version 3] " Carl Love
2022-04-17 16:23           ` Joel Brobecker
2022-04-18 19:21             ` [PATCH 1/2 Version 5] " Carl Love
2022-04-22 19:49               ` [PATCH 1/2 Version 5 Ping] " Carl Love
2022-04-24 16:50               ` [PATCH 1/2 Version 5] " Joel Brobecker
2022-04-25 15:58                 ` [PATCH 1/2 Version 6] " Carl Love
2022-04-26 18:05                   ` Joel Brobecker
2022-03-04 19:53 ` [PATCH 2/2] " Carl Love
2022-03-06 12:42   ` Joel Brobecker
2022-04-12 17:09     ` [PATCH 2/2 Version 2] " Carl Love
2022-04-13 14:12       ` will schmidt
2022-04-13 21:38         ` [PATCH 2/2 Version 3] " Carl Love
2022-04-14 13:05           ` Pedro Alves
2022-04-14 20:20             ` [PATCH 2/2 Version 4] " Carl Love
2022-04-14 20:43               ` Carl Love
2022-04-17 16:48                 ` Joel Brobecker
2022-04-18 19:21                   ` [PATCH 2/2 Version 5] " Carl Love
2022-04-22 19:47                     ` [PATCH 2/2 Version 5 PING] " Carl Love
2022-04-24 16:56                     ` [PATCH 2/2 Version 5] " Joel Brobecker
2022-04-12 17:09 ` [PATCH 0/2 Version 2] " Carl Love

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=7ff0655bead2a8245018fbf9624f207cd38a5b7f.camel@us.ibm.com \
    --to=cel@us.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=rogealve@br.ibm.com \
    --cc=tuliom@linux.ibm.com \
    --cc=will_schmidt@vnet.ibm.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).