From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] Use aarch64_decode_insn more in GDB
Date: Thu, 05 Nov 2015 09:54:00 -0000 [thread overview]
Message-ID: <563B2758.6030707@redhat.com> (raw)
In-Reply-To: <86lhacye32.fsf@gmail.com>
On 11/05/2015 09:45 AM, Yao Qi wrote:
> Yao Qi <qiyaoltc@gmail.com> writes:
>
>> This patch series changes GDB aarch64 backend to using aarch64_decode_insn
>> to decode instructions. Patch 1 is the preparatory patch, and patch 2
>> and 3 do the change.
>>
>> Regression tested on aarch64-linux.
>
> I pushed them in.
>
Just wanted to say that I enjoy seeing all these code sharing cleanups.
Thanks for doing this.
--
Pedro Alves
next prev parent reply other threads:[~2015-11-05 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 16:47 Yao Qi
2015-10-29 16:51 ` [PATCH 2/3] Use aarch64_decode_insn in aarch64_analyze_prologue Yao Qi
2015-10-29 17:05 ` [PATCH 1/3] Combine aarch64_decode_stp_offset_wb and aarch64_decode_stp_offset Yao Qi
2015-10-29 17:09 ` [PATCH 3/3] Use aarch64_decode_insn in aarch64_displaced_step_copy_insn Yao Qi
2015-11-05 9:45 ` [PATCH 0/3] Use aarch64_decode_insn more in GDB Yao Qi
2015-11-05 9:54 ` Pedro Alves [this message]
2015-11-05 10:35 ` 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=563B2758.6030707@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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