From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: gdb-patches@sourceware.org, Nigel Stephens <nigel@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: Disassemble branch delay slot instructions automatically
Date: Wed, 16 May 2007 15:32:00 -0000 [thread overview]
Message-ID: <20070516153242.GA8062@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0705151913050.31736@perivale.mips.com>
On Tue, May 15, 2007 at 07:13:41PM +0100, Maciej W. Rozycki wrote:
> Hello,
>
> This is a change that implements automatic disassembly of instructions in
> a branch delay slot if a branch is the last instruction to be output. It
> is especially useful with the "display /i" command when single-stepping,
> where you may want to see a single instruction normally not to get
> distracted, but with a branch an intruction that follows would be executed
> without having been printed.
>
> Here is an example for MIPS machine code -- this is with our current
> implementation:
>
> (gdb) x /i 0x801018a4
> 0x801018a4 <pthread_create+52>: beqz v0,0x80101a10 <pthread_create+416>
>
> and here -- the same command with the patch applied:
>
> (gdb) x /i 0x801018a4
> 0x801018a4 <pthread_create+52>: beqz v0,0x80101a10 <pthread_create+416>
> 0x801018a8 <pthread_create+56>: li v1,11
>
> This change has been tested natively for mips-unknown-linux-gnu and
> remotely for mipsisa32-sde-elf, using mips-sim-sde32/-EB and
> mips-sim-sde32/-EL as the targets, with no regressions.
I would like additional opinions on this patch.
My first reaction was "hey, that would be useful to me", but my second
was concern that this would upset a GDB/MI frontend. We should at
least try to provoke a problem in one such frontend first.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-05-16 15:32 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 [this message]
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
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=20070516153242.GA8062@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@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