From: Marcus Shawcroft <marcus.shawcroft@arm.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] aarch64-tdep basic port.
Date: Fri, 25 Jan 2013 19:00:00 -0000 [thread overview]
Message-ID: <5102D61B.7010609@arm.com> (raw)
In-Reply-To: <5102D5E2.8080405@redhat.com>
On 25/01/13 18:58, Pedro Alves wrote:
> On 01/25/2013 06:54 PM, Marcus Shawcroft wrote:
>> On 25/01/13 17:58, Pedro Alves wrote:
>>
>>> Okay. Seems odd to me to just be clear the low bits and
>>> doing nothing else if they're "reserved", instead of waiting
>>> until they do have some meaning (at which point GDB will
>>> necessarily need to learn to do something about them). Does
>>> actually end up seeing non-4 bytes instructions today somehow?
>>
>> It would be safe to remove this masking code today, if you prefer.
>
> I would. One place less for us to worry about if we want to
> change this interface before you define the bits.
>
> (I'll be looking at the gdbserver/native patches next)
>
Ok, I'll re-spin without.
/M
next prev parent reply other threads:[~2013-01-25 19:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 13:54 Marcus Shawcroft
2013-01-25 17:59 ` Pedro Alves
2013-01-25 18:55 ` Marcus Shawcroft
2013-01-25 18:59 ` Pedro Alves
2013-01-25 19:00 ` Marcus Shawcroft [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-28 9:54 Marcus Shawcroft
2013-02-01 14:52 ` Pedro Alves
2013-01-22 17:39 Marcus Shawcroft
2013-01-23 5:21 ` Sergio Durigan Junior
2013-01-23 9:43 ` Richard Earnshaw
2013-01-23 11:13 ` Joel Brobecker
2013-01-24 20:03 ` Pedro Alves
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=5102D61B.7010609@arm.com \
--to=marcus.shawcroft@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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