public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] gdbarch software_single_step frame_info to regcache: alpha
Date: Tue, 22 Nov 2016 16:56:00 -0000 [thread overview]
Message-ID: <7ab2d0874025af6ee858b32c576f2461c0a1df3d@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 7ab2d0874025af6ee858b32c576f2461c0a1df3d ***
Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7ab2d0874025af6ee858b32c576f2461c0a1df3d
gdbarch software_single_step frame_info to regcache: alpha
gdb:
2016-11-22 Yao Qi <yao.qi@linaro.org>
* alpha-tdep.c (alpha_deal_with_atomic_sequence): Call
get_regcache_arch instead of get_frame_arch. Call
regcache_read_pc instead of get_frame_pc.
(alpha_next_pc): Replace parameter frame with regcache.
Call regcache_raw_get_unsigned instead of
get_frame_register_unsigned.
next reply other threads:[~2016-11-22 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 16:56 sergiodj+buildbot [this message]
2016-11-22 16:46 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
2016-11-22 17:09 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-11-22 17:43 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot
2016-11-22 18:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-11-22 18:39 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-11-22 20:02 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-11-30 12:03 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-11-30 12:24 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-12-04 1:25 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-12-04 1:49 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2016-12-04 1:49 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
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=7ab2d0874025af6ee858b32c576f2461c0a1df3d@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--cc=gdb-testers@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).