Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
		"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH 1/3] [aarch64] Remove argument pc from disas_aarch64_insn
Date: Fri, 02 Oct 2015 12:30:00 -0000	[thread overview]
Message-ID: <CAFqB+PwfwKEQ8=kn-gbSVB2MVkwO7y_SMsU==BuawUofx48zgQ@mail.gmail.com> (raw)
In-Reply-To: <1443785039-24602-2-git-send-email-yao.qi@linaro.org>

On 2 October 2015 at 12:23, Yao Qi <qiyaoltc@gmail.com> wrote:
> I happen to see that argument pc is not used inside disas_aarch64_insn
> at all.  This patch is to remove it.
>
> OK to apply?
>
> opcodes:
>
> 2015-10-01  Yao Qi  <yao.qi@linaro.org>
>
>         * aarch64-dis.c (disas_aarch64_insn): Remove argument PC.
>         (print_insn_aarch64_word): Caller updated.

Ok /Marcus


  reply	other threads:[~2015-10-02 12:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 16:35 [PATCH 0/2] [aarch64] Use opcodes to decode instructions in GDB Yao Qi
2015-10-01 16:35 ` [PATCH 1/2] [aarch64] Remove argument pc from disas_aarch64_insn Yao Qi
2015-10-01 16:36 ` [PATCH 2/2] [aarch64] Use opcodes to decode instructions in GDB Yao Qi
2015-10-02  7:51   ` Marcus Shawcroft
2015-10-02 11:24     ` [PATCH 0/3 V2] " Yao Qi
2015-10-02 11:24       ` [PATCH 3/3] [aarch64] use aarch64_decode_insn " Yao Qi
2015-10-07  8:56         ` Yao Qi
2015-10-02 11:24       ` [PATCH 1/3] [aarch64] Remove argument pc from disas_aarch64_insn Yao Qi
2015-10-02 12:30         ` Marcus Shawcroft [this message]
2015-10-02 11:24       ` [PATCH 2/3] [aarch64] expose disas_aarch64_insn and rename it to aarch64_decode_insn Yao Qi
2015-10-02 12:35         ` Marcus Shawcroft
2015-10-02 14:32           ` 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='CAFqB+PwfwKEQ8=kn-gbSVB2MVkwO7y_SMsU==BuawUofx48zgQ@mail.gmail.com' \
    --to=marcus.shawcroft@gmail.com \
    --cc=binutils@sourceware.org \
    --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