public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/17945] aarch64 lacks "deal_with_atomic_sequence"
Date: Wed, 11 Mar 2015 10:25:00 -0000 [thread overview]
Message-ID: <bug-17945-4717-dWjQIbmdLG@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17945-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17945
--- Comment #5 from Yao Qi <qiyao at gcc dot gnu.org> ---
(In reply to Michael Hudson-Doyle from comment #4)
> Oh, hm. How long has that been there? If it's actually supposed to be
It was added in April 2014,
commit 9404b58f46328b3b171b0d5eeb0691bd685bc4f5
Author: Kyle McMartin <kmcmarti@redhat.com>
Date: Wed Apr 30 12:04:50 2014 -0400
aarch64: detect atomic sequences like other ll/sc architectures
gdb/Changelog:
* aarch64-tdep.c (aarch64_software_single_step): New function.
(aarch64_gdbarch_init): Handle single stepping of atomic sequences
with aarch64_software_single_step.
gdb/testsuite/ChangeLog:
* gdb.arch/aarch64-atomic-inst.c: New file.
* gdb.arch/aarch64-atomic-inst.exp: New file.
> working, I'll definitely try to reproduce!
That will be great!
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-03-11 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 22:02 [Bug tdep/17945] New: " michael.hudson at canonical dot com
2015-02-08 22:06 ` [Bug tdep/17945] " michael.hudson at canonical dot com
2015-02-24 23:24 ` qiyao at gcc dot gnu.org
2015-03-06 20:15 ` qiyao at gcc dot gnu.org
2015-03-09 2:03 ` michael.hudson at canonical dot com
2015-03-10 14:07 ` qiyao at gcc dot gnu.org
2015-03-10 22:10 ` michael.hudson at canonical dot com
2015-03-11 10:25 ` qiyao at gcc dot gnu.org [this message]
2015-04-24 15:32 ` qiyao at gcc dot gnu.org
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=bug-17945-4717-dWjQIbmdLG@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).