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] common: cgen-mem/cgen-ops: fix extern inline handling
Date: Tue, 31 Mar 2015 08:58:00 -0000	[thread overview]
Message-ID: <5a394431deb3745c04a74d2a109aca075f79afd6@kwanyin> (raw)

*** TEST RESULTS FOR COMMIT 5a394431deb3745c04a74d2a109aca075f79afd6 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 5a394431deb3745c04a74d2a109aca075f79afd6

common: cgen-mem/cgen-ops: fix extern inline handling
With newer versions of gcc (5.x), the extern inline we're using with the
cgen-{mem,ops} modules no longer work.  Since this code really wants the
gnu inline semantics, use that attribute explicitly.


             reply	other threads:[~2015-03-31  7:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31  8:58 sergiodj+buildbot [this message]
2015-03-31  9:07 ` Failures on Fedora-ppc64be-cc-with-index, branch master sergiodj+buildbot
2015-03-31  9:26 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2015-03-31 12:19 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2015-03-31 12:55 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-03-31 19:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-04-01 16:27 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2015-04-01 17:00 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2015-04-01 17:29 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2015-04-03  5:17 ` Failures on Fedora-i686, " sergiodj+buildbot
2015-04-03  6:09 ` Failures on Fedora-x86_64-cc-with-index, " 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=5a394431deb3745c04a74d2a109aca075f79afd6@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).