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: convert to bfd_endian
Date: Sun, 03 Jan 2016 05:29:00 -0000	[thread overview]
Message-ID: <1ac72f0659d64d6a14da862242db0d841d2878d0@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 1ac72f0659d64d6a14da862242db0d841d2878d0 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 1ac72f0659d64d6a14da862242db0d841d2878d0

sim: convert to bfd_endian

Rather than re-invent endian defines, as well as maintain our own list
of OS & arch-specific includes, punt all that logic in favor of the bfd
ones already set up and maintained elsewhere.  We already rely on the
bfd library, so leveraging the endian aspect should be fine.


             reply	other threads:[~2016-01-03  5:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-03  5:29 sergiodj+buildbot [this message]
2016-01-03  5:29 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2016-01-03  5:29 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-01-03  5:32 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2016-01-03  5:33 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-01-03  5:34 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-01-03  5:36 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-01-03  5:36 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2016-01-03  5:38 ` Failures on Debian-i686, " sergiodj+buildbot
2016-01-03  5:46 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-03  5:50 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-01-03  5:51 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-03  5:57 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2016-01-03  6:03 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-01-03  6:07 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-03  6:20 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-01-03  6:21 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-01-03  6:32 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-01-03  6:41 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-03  6:42 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-01-03  7:00 ` Failures on Fedora-ppc64le-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=1ac72f0659d64d6a14da862242db0d841d2878d0@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).