public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: nickc@redhat.com
Subject: [PATCH 0/4] sim: unify disassmebly tracing logic
Date: Thu, 31 Dec 2015 04:32:00 -0000	[thread overview]
Message-ID: <1451536348-31380-1-git-send-email-vapier@gentoo.org> (raw)

Nick: could you give the msp430/aarch64 changes a glance before i push ?

Mike Frysinger (4):
  sim: trace: add support for disassembling
  sim: msp430: switch to common disassembler tracing
  sim: bfin: add support disasm tracing
  sim: aarch64: switch to common disassembler tracing

 sim/aarch64/interp.c    |  96 ---------------
 sim/aarch64/memory.c    |   2 -
 sim/aarch64/simulator.c |  49 ++------
 sim/aarch64/simulator.h |   3 -
 sim/bfin/interp.c       |   2 +
 sim/common/sim-trace.c  |  62 ++++++++++
 sim/common/sim-trace.h  |  40 +++++-
 sim/msp430/Makefile.in  |   1 -
 sim/msp430/msp430-sim.c |  40 +-----
 sim/msp430/trace.c      | 320 ------------------------------------------------
 sim/msp430/trace.h      |  28 -----
 11 files changed, 118 insertions(+), 525 deletions(-)
 delete mode 100644 sim/msp430/trace.c
 delete mode 100644 sim/msp430/trace.h

-- 
2.6.2

             reply	other threads:[~2015-12-31  4:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-31  4:32 Mike Frysinger [this message]
2015-12-31  4:32 ` [PATCH 3/4] sim: bfin: add support disasm tracing Mike Frysinger
2015-12-31  4:32 ` [PATCH 2/4] sim: msp430: switch to common disassembler tracing Mike Frysinger
2015-12-31  4:32 ` [PATCH 1/4] sim: trace: add support for disassembling Mike Frysinger
2015-12-31  4:40 ` [PATCH 4/4] sim: aarch64: switch to common disassembler tracing Mike Frysinger
2016-01-05 16:54 ` [PATCH 0/4] sim: unify disassmebly tracing logic Nick Clifton

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=1451536348-31380-1-git-send-email-vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@redhat.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).