From: Kyle McMartin <kmcmarti@redhat.com>
To: Marcus Shawcroft <marcus.shawcroft@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCHv2] aarch64: detect atomic sequences like other ll/sc architectures
Date: Thu, 27 Mar 2014 16:37:00 -0000 [thread overview]
Message-ID: <20140327163720.GK3075@redacted.bos.redhat.com> (raw)
In-Reply-To: <CAFqB+PyPpHUr+7TSzaKwfPShcDHGi9Zmer0RBiNXJpuQ3eQFug@mail.gmail.com>
On Thu, Mar 27, 2014 at 04:12:55PM +0000, Marcus Shawcroft wrote:
> >> This also looks wrong.
> >>
> >
> > Eh... I tested all 24 possible ldxr/stxr opcodes...
>
> Kyle
> You are right, sorry, I can't read the encoding tables. This mask and
> pattern is indeed sensible.
>
No worries at all, I'm glad you made me double check. :)
--Kyle
prev parent reply other threads:[~2014-03-27 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 1:51 Kyle McMartin
2014-03-27 13:07 ` Joel Brobecker
2014-03-27 15:45 ` Kyle McMartin
2014-03-27 14:07 ` Marcus Shawcroft
2014-03-27 15:40 ` Kyle McMartin
2014-03-27 16:13 ` Marcus Shawcroft
2014-03-27 16:37 ` Kyle McMartin [this message]
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=20140327163720.GK3075@redacted.bos.redhat.com \
--to=kmcmarti@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=marcus.shawcroft@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