public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Richard Henderson <rth@twiddle.net>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH 2/2] aarch64: Decode dwarf2 register numbers
Date: Wed, 03 Sep 2014 10:27:00 -0000	[thread overview]
Message-ID: <CAFqB+PyG4jXD7O9JXNqbDGapzofs52LbjEwfUEgYLTQFbvhS_A@mail.gmail.com> (raw)
In-Reply-To: <CAFqB+PzOWkvTmC3WmNgCGLC-1+QomXhSfHL9pu_mutj7Bft77Q@mail.gmail.com>

On 3 September 2014 11:24, Marcus Shawcroft <marcus.shawcroft@gmail.com> wrote:
> On 7 August 2014 01:11, Richard Henderson <rth@twiddle.net> wrote:
>> Similar to the parsing side in gas.  But here I'm less
>> certain about only printing dN, since these are also used
>> for uses within .debug_info which could rightly use vN.
>
>> +   "d0",  "d1",  "d2",  "d3",  "d4",  "d5",  "d6",  "d7",
>> +   "d8",  "d9", "d10", "d11", "d12", "d13", "d14", "d15",
>> +  "d16", "d17", "d18", "d19", "d20", "d21", "d22", "d23",
>> +  "d24", "d25", "d26", "d27", "d28", "d29", "d30", "d31",
>
>
> I think these should be Vn rather than dN.

Oops, ignore me, I see you made that change in the version of the
patch you pushed...

/Marcus

  reply	other threads:[~2014-09-03 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07  0:09 [PATCH 1/2] aarch64: Fix dwarf2 regnum for Dn Richard Henderson
2014-08-07  0:09 ` [PATCH 2/2] aarch64: Decode dwarf2 register numbers Richard Henderson
2014-09-03 10:25   ` Marcus Shawcroft
2014-09-03 10:27     ` Marcus Shawcroft [this message]
2014-09-02 17:38 ` [PATCH 1/2] aarch64: Fix dwarf2 regnum for Dn Marcus Shawcroft

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+PyG4jXD7O9JXNqbDGapzofs52LbjEwfUEgYLTQFbvhS_A@mail.gmail.com \
    --to=marcus.shawcroft@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=rth@twiddle.net \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).