From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: gdb-patches@sourceware.org, Chris Dearman <chris@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: mips-tdep.c: Adjust breakpoints in branch delay slots
Date: Fri, 25 May 2007 13:26:00 -0000 [thread overview]
Message-ID: <20070525132646.GA29896@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0705251419160.13913@perivale.mips.com>
On Fri, May 25, 2007 at 02:20:55PM +0100, Maciej W. Rozycki wrote:
> > BTW, see mips_single_step_through_delay, which could probably be
> > improved. Doesn't its comment about MIPS16 having no delay slots
> > disagree with this patch? Which is right?
>
> There are both kinds of jumps/branches in MIPS16e:
>
> - jal, jalr, jalx and jr do have a delay slot,
>
> - branches and jalrc and jrc have no delay slot (the two latters are
> MIPS16e additions over "traditional" MIPS16).
You might want to fix mips_single_step_through_delay at some point,
then; it doesn't know about any MIPS16 instructions with delay slots.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-05-25 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 18:08 Maciej W. Rozycki
2007-05-24 18:21 ` Mark Kettenis
2007-05-24 18:31 ` Daniel Jacobowitz
[not found] ` <Pine.LNX.4.61.0705251217190.13913@perivale.mips.com>
2007-05-25 12:50 ` Maciej W. Rozycki
2007-05-25 13:16 ` Maciej W. Rozycki
[not found] ` <Pine.LNX.4.61.0705251318500.13913@perivale.mips.com>
2007-05-25 13:19 ` Daniel Jacobowitz
2007-06-15 14:38 ` Maciej W. Rozycki
2007-05-25 13:21 ` Maciej W. Rozycki
2007-05-25 13:26 ` Daniel Jacobowitz [this message]
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=20070525132646.GA29896@caradoc.them.org \
--to=drow@false.org \
--cc=chris@mips.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=macro@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