From: Pedro Alves <palves@redhat.com>
To: Kyle McMartin <kmcmarti@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] aarch64: detect atomic sequences like other ll/sc architectures
Date: Mon, 24 Mar 2014 16:25:00 -0000 [thread overview]
Message-ID: <53305C5A.5000001@redhat.com> (raw)
In-Reply-To: <20140324161056.GB23291@redacted.bos.redhat.com>
Hi!
On 03/24/2014 04:10 PM, Kyle McMartin wrote:
> Add similar single-stepping over atomic sequences support like other
> load-locked/store-conditional architectures (alpha, powerpc, arm, etc.)
> do. Verified the decode_masked_match, and decode_bcond works against the
> atomic sequences used in the Linux kernel atomic.h, and also gcc
> libatomic. Thanks to Richard Henderson for feedback on my initial
> attempt at this patch!
Thanks! It'd be nice to have a test in the test suite. Could you
add one?
PPC64's equivalent seems to be gdb.arch/ppc64-atomic-inst.c|exp.
--
Pedro Alves
next prev parent reply other threads:[~2014-03-24 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 16:11 Kyle McMartin
2014-03-24 16:25 ` Pedro Alves [this message]
2014-03-24 16:28 ` Kyle McMartin
2014-03-24 16:57 ` Joel Brobecker
2014-03-24 18:00 ` Richard Earnshaw
2014-03-27 1:52 ` Kyle McMartin
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=53305C5A.5000001@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kmcmarti@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