From: Yao Qi <yao@codesourcery.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [try 2nd 5/8] Displaced stepping for Thumb 32-bit insns
Date: Sun, 09 Oct 2011 13:28:00 -0000 [thread overview]
Message-ID: <4E91A158.5000306@codesourcery.com> (raw)
In-Reply-To: <201109141339.p8EDddLk024568@d06av02.portsmouth.uk.ibm.com>
On 09/14/2011 09:39 PM, Ulrich Weigand wrote:
>> > 1. Failures in gdb.arch/thumb2-it.exp and gdb.base/gdb1555.exp.
>> > These failures are caused by missing IT support in thumb displaced stepping.
> Ah, right. Fortunately, I think IT support should be relatively easy to
> add, in fact we should be able to just completely emulate it:
>
> - The first thing we do when we're about to displaced-step a Thumb insn
> is to check the itstate and see whether we're in an IT block.
>
> - If so, we check whether the condition is true, given the current state
> of the flags.
>
> - If the condition is false, we always use a NOP as the displaced
> instruction; otherwise, compute the displaced instruction as usual.
>
> - In either case, set the CSPR register as if we're outside of any
> IT block while actually executing the displaced instruction. (This
> also makes sure that the breakpoint at the end will always be
> executed.)
>
> - During fixup after execution is done, re-set IT state in the CSPR
> to the proper value (advanced by one instruction).
>
> See also thumb_get_next_pc_raw for how to manipulate IT state ...
>
> Does this look good to you?
>
Yes, it looks right to me in general. However, it doesn't handle the
case of `stepi' in condition blocks when displaced stepping is enabled,
as gdb.arch/thumb2-it.exp tested. We expect inferior stops at the next
true-condition instruction instead of next instruction after typing
`stepi'. In this design, inferior will stop at the next instruction
regardless of condition. We may adjust PC value in fixup to skip these
false-condition instructions.
--
Yao (é½å°§)
next prev parent reply other threads:[~2011-10-09 13:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201107151847.p6FIlJNm001180@d06av02.portsmouth.uk.ibm.com>
2011-08-06 4:32 ` Yao Qi
2011-08-09 18:46 ` Ulrich Weigand
2011-08-19 3:13 ` Yao Qi
2011-08-19 16:39 ` Ulrich Weigand
2011-08-30 15:53 ` Yao Qi
2011-09-14 14:25 ` Ulrich Weigand
2011-10-09 13:28 ` Yao Qi [this message]
2011-10-10 14:40 ` Ulrich Weigand
2011-10-10 1:41 ` Yao Qi
2011-10-10 14:39 ` Ulrich Weigand
2010-12-25 14:17 [patch 0/3] Displaced stepping for 16-bit Thumb instructions Yao Qi
2011-03-24 13:49 ` [try 2nd 0/8] Displaced stepping for " Yao Qi
2011-03-24 14:05 ` [try 2nd 5/8] Displaced stepping for Thumb 32-bit insns Yao Qi
2011-05-05 13:25 ` Yao Qi
2011-05-17 17:14 ` Ulrich Weigand
2011-05-23 11:32 ` Yao Qi
2011-05-23 11:32 ` Yao Qi
2011-05-27 22:11 ` Ulrich Weigand
2011-07-06 10:55 ` Yao Qi
2011-07-15 19:57 ` Ulrich Weigand
2011-07-18 9:26 ` Yao Qi
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=4E91A158.5000306@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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