From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: yao@codesourcery.com (Yao Qi)
Cc: gdb-patches@sourceware.org (gdb-patches@sourceware.org)
Subject: Re: [try 2nd 5/8] Displaced stepping for Thumb 32-bit insns
Date: Fri, 19 Aug 2011 16:39:00 -0000 [thread overview]
Message-ID: <201108191639.p7JGdC8H007859@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <4E4DD4C6.9060700@codesourcery.com> from "Yao Qi" at Aug 19, 2011 11:13:10 AM
Yao Qi wrote:
> Support displaced stepping for Thumb 32-bit insns.
>
> * arm-tdep.c (thumb_copy_unmodified_32bit): New.
> (thumb2_copy_preload): New.
> (thumb2_copy_copro_load_store): New.
> (thumb2_copy_b_bl_blx): New.
> (thumb2_copy_alu_imm): New.
> (thumb2_copy_load_reg_imm): New.
> (thumb2_copy_load_literal): New
> (thumb2_copy_block_xfer): New.
> (thumb_32bit_copy_undef): New.
> (thumb_32bit_copy_unpred): New.
> (thumb2_decode_ext_reg_ld_st): New.
> (thumb2_decode_svc_copro): New.
> (decode_thumb_32bit_store_single_data_item): New.
> (thumb_copy_pc_relative_32bit): New.
> (thumb_decode_pc_relative_32bit): New.
> (decode_thumb_32bit_ld_mem_hints): New.
> (thumb2_copy_table_branch): New
> (thumb_process_displaced_32bit_insn): Process Thumb 32-bit
> instructions.
I'm not finding any more bugs :-)
Just a couple of cosmetic issues:
> + /* PC is only allowed to use in PLI (immeidate,literal) Encoding T3, and
Typo: immediate
> + case 1: /* Load halfword and memory hints. */
> + if (rt == 0xf) /* PLD{W} and Unalloc memory hint. */
> + return thumb_copy_unmodified_32bit (gdbarch, insn1, insn2,
> + "pld/unalloc memhint", dsc);
> + else
> + {
> + int insn2_bit_8_11 = bits (insn2, 8, 11);
This is now unused.
Since this is (together with the previous patches that are not yet committed)
is a significant change, I'm wondering a bit what additional testing we could
do to catch any possibly remaining issues ...
Did you try a testsuite run with a GDB build that forces displaced-stepping
on by default? (I.e. change the initializer of can_use_displaced_stepping
in infrun.c to can_use_displaced_stepping_on.) That would exercise the new
code a lot.
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2011-08-19 16:39 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 [this message]
2011-08-30 15:53 ` Yao Qi
2011-09-14 14:25 ` Ulrich Weigand
2011-10-09 13:28 ` Yao Qi
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-27 22:11 ` Ulrich Weigand
2011-05-23 11:32 ` Yao Qi
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=201108191639.p7JGdC8H007859@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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