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] sim: bfin: split out common mach/model defines into arch.h [PR sim/20438]
Date: Sun, 14 Aug 2016 01:05:00 -0000	[thread overview]
Message-ID: <474a2d9f5f8a080e30812525729c3a8b7baa61d6@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 474a2d9f5f8a080e30812525729c3a8b7baa61d6 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 474a2d9f5f8a080e30812525729c3a8b7baa61d6

sim: bfin: split out common mach/model defines into arch.h [PR sim/20438]

The current machs.h mixes common enums with Blackfin-specific defines.
This causes us troubles with header inclusion order such that we can't
drop the old SIM_CPU typedef (which is duplicated in common code).  By
splitting the two up, we can unwind this dependency chain, and drop the
old typedef.  It also fixes building with older gcc versions.


             reply	other threads:[~2016-08-13 20:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14  1:05 sergiodj+buildbot [this message]
2016-08-14  1:03 ` Failures on Fedora-i686, branch master sergiodj+buildbot
2016-08-14  5:52 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-08-14  5:55 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2016-08-14  6:24 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-08-14  6:44 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-08-14  6:59 ` Failures on Debian-i686, " sergiodj+buildbot
2016-08-14  7:00 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-08-14  7:24 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-08-14  7:55 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-08-14  8:32 ` 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=474a2d9f5f8a080e30812525729c3a8b7baa61d6@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).