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: use common configure options
Date: Mon, 30 Mar 2015 06:48:00 -0000 [thread overview]
Message-ID: <ca968da465a0d1fd153b158b7aa69730709f43db@kwanyin> (raw)
*** TEST RESULTS FOR COMMIT ca968da465a0d1fd153b158b7aa69730709f43db ***
Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: ca968da465a0d1fd153b158b7aa69730709f43db
sim: cr16: use common configure options
In preparation for converting to nrun, call the common functions that
are needed. This doesn't produce any new warnings, and the generated
code should be the same.
next reply other threads:[~2015-03-30 5:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 6:48 sergiodj+buildbot [this message]
2015-03-30 6:48 ` Failures on Fedora-ppc64be-cc-with-index, branch master sergiodj+buildbot
2015-03-30 7:07 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2015-03-30 7:19 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2015-03-30 7:26 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-03-30 13:18 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-03-30 16:00 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-03-30 16:13 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2015-03-30 17:55 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2015-04-01 19:43 ` Failures on Fedora-i686, " sergiodj+buildbot
2015-04-01 20:22 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-04-01 20:40 ` Failures on Fedora-x86_64-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=ca968da465a0d1fd153b158b7aa69730709f43db@kwanyin \
--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).