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] Make gdbserver find_register_by_number static
Date: Fri, 23 Mar 2018 15:04:00 -0000 [thread overview]
Message-ID: <dff7492c9b221aacd4efa6675bb288dfb5d50f80@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT dff7492c9b221aacd4efa6675bb288dfb5d50f80 ***
Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: dff7492c9b221aacd4efa6675bb288dfb5d50f80
Make gdbserver find_register_by_number static
gdbserver/
* regcache.c (find_register_by_number): Make static.
(find_regno): Use find_register_by_number
* regcache.h (struct reg): Remove declaration.
next reply other threads:[~2018-03-23 15:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 15:04 sergiodj+buildbot [this message]
2018-03-23 15:04 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-03-23 15:05 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-03-23 15:24 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-03-23 15:32 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-03-23 15:36 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-03-23 15:44 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot
2018-03-23 15:44 ` Failures on Fedora-i686, branch master sergiodj+buildbot
2018-03-23 15:51 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-23 15:55 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-03-23 16:18 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " 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=dff7492c9b221aacd4efa6675bb288dfb5d50f80@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).