Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: gdb-patches@sourceware.org, insight@sourceware.org,
		Nigel Stephens <nigel@mips.com>,
		"Maciej W. Rozycki" <macro@linux-mips.org>,
		Eli Zaretskii <eliz@gnu.org>
Subject: Re: Disassemble branch delay slot instructions automatically
Date: Wed, 20 Jun 2007 14:09:00 -0000	[thread overview]
Message-ID: <20070620140925.GA29461@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0706151547560.30938@perivale.mips.com>

On Wed, Jun 20, 2007 at 02:56:20PM +0100, Maciej W. Rozycki wrote:
> On Wed, 13 Jun 2007, Daniel Jacobowitz wrote:
> 
> > I think the patch is pretty much OK, except for the use of
> > TARGET_PRINT_INSN.  We're trying to eliminate the gdbarch macros now.
> > I think the best solution would be to add the extra argument to
> > gdb_print_insn; it's only used here and in the TUI.
> 
>  And also in Insight; I have updated that too.  I suppose the plan is to 
> substitute TARGET_PRINT_INSN with gdbarch_print_insn(), but that should be 
> done separately, so that it is not mixed with functional changes.

In fact, it happened yesterday.

2007-06-19  Markus Deuling  <deuling@de.ibm.com>

        * gdbarch.sh (TARGET_PRINT_INSN): Replace by
	gdbarch_print_insn.
        * disasm.c (dump_insns, gdb_print_insn): Likewise.
        * gdbarch.c, gdbarch.h: Regenerate.

So I imagine you need to refresh this patch.  I was actually
suggesting you add the disassemble_info argument to gdb_print_insn,
not the number of delay slots; but this way seems fine too.

This version is OK, if Eli likes the NEWS entry and you add a
Makefile.in update (since you added #include's).  Eli, is the below
OK?

> Index: binutils-quilt/src/gdb/NEWS
> ===================================================================
> --- binutils-quilt.orig/src/gdb/NEWS	2007-06-19 12:24:32.000000000 +0100
> +++ binutils-quilt/src/gdb/NEWS	2007-06-19 15:16:19.000000000 +0100
> @@ -41,6 +41,9 @@
>  layout.  It also supports a TextSeg= and DataSeg= response when only
>  segment base addresses (rather than offsets) are available.
>  
> +* The /i format now outputs any trailing branch delay slot instructions 
> +immediately following the last instruction within the count specified.
> +
>  * New commands
>  
>  set remoteflow
> 

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-06-20 14:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 18:13 Maciej W. Rozycki
2007-05-16 15:32 ` Daniel Jacobowitz
2007-05-18 15:47   ` Maciej W. Rozycki
2007-06-13 16:56     ` Daniel Jacobowitz
2007-06-20 13:56       ` Maciej W. Rozycki
2007-06-20 14:09         ` Daniel Jacobowitz [this message]
2007-06-20 15:25           ` Maciej W. Rozycki
2007-06-20 18:37         ` Eli Zaretskii
2007-06-21 15:19           ` Maciej W. Rozycki
2007-06-21 19:01             ` Eli Zaretskii

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=20070620140925.GA29461@caradoc.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=insight@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=macro@mips.com \
    --cc=nigel@mips.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