From: Eli Zaretskii <eliz@gnu.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: drow@false.org, gdb-patches@sourceware.org,
insight@sourceware.org, nigel@mips.com,
macro@linux-mips.org
Subject: Re: Disassemble branch delay slot instructions automatically
Date: Wed, 20 Jun 2007 18:37:00 -0000 [thread overview]
Message-ID: <u645iqxpb.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0706151547560.30938@perivale.mips.com> (macro@mips.com)
> Date: Wed, 20 Jun 2007 14:56:20 +0100 (BST)
> From: "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>
>
> 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.
> +
This is fine, but I think we should also document this in the user
manual.
next prev parent reply other threads:[~2007-06-20 18:37 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
2007-06-20 15:25 ` Maciej W. Rozycki
2007-06-20 18:37 ` Eli Zaretskii [this message]
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=u645iqxpb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.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