public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] sim: cr16: push down sd/cpu vars
Date: Mon, 16 Nov 2015 04:30:00 -0000 [thread overview]
Message-ID: <267b3b8e068f5043419991175bdbc56eb7a575be@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 267b3b8e068f5043419991175bdbc56eb7a575be ***
Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 267b3b8e068f5043419991175bdbc56eb7a575be
sim: cr16: push down sd/cpu vars
By itself, this commit doesn't really change anything. It lays the
groundwork for using the cpu state in follow up commits, both for
engine state and for cpu state. Splitting things up this way so it
is easier to see how things have changed.
next reply other threads:[~2015-11-16 4:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 4:30 sergiodj+buildbot [this message]
2015-11-16 4:31 ` Failures on Debian-s390x-native-gdbserver-m64, branch master sergiodj+buildbot
2015-11-16 4:37 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2015-11-16 4:46 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-11-16 4:47 ` Failures on Fedora-i686, " sergiodj+buildbot
2015-11-16 4:55 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2015-11-16 5:04 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-11-16 5:07 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2015-11-16 5:14 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2015-11-16 5:16 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2015-11-16 6:03 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2015-11-16 8:24 ` Failures on Debian-i686, " sergiodj+buildbot
2015-11-16 8:53 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2015-11-16 9:17 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-11-16 10:42 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2015-11-16 10:54 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-11-16 12:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-11-16 13:08 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-11-16 14:18 ` 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=267b3b8e068f5043419991175bdbc56eb7a575be@gdb-build \
--to=sergiodj+buildbot@redhat.com \
--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).