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] mips64 rtype_to_howto error status
Date: Wed, 07 Mar 2018 07:01:00 -0000 [thread overview]
Message-ID: <0118219e1850a05ceb181a4f47a6906c01c17c83@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 0118219e1850a05ceb181a4f47a6906c01c17c83 ***
Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 0118219e1850a05ceb181a4f47a6906c01c17c83
mips64 rtype_to_howto error status
* elf64-mips.c (mips_elf64_rtype_to_howto): Return NULL on error.
(mips_elf64_slurp_one_reloc_table): Pass on error.
next reply other threads:[~2018-03-07 7:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 7:01 sergiodj+buildbot [this message]
2018-03-07 7:01 ` Failures on Debian-s390x-m64, branch master sergiodj+buildbot
2018-03-07 7:10 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-03-07 7:13 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-07 7:16 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-03-07 7:20 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-03-07 7:25 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-03-07 7:39 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-03-07 7:58 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-07 8:05 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2018-03-07 8:11 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-03-07 8:27 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-03-07 21:01 ` Failures on Ubuntu-AArch64-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=0118219e1850a05ceb181a4f47a6906c01c17c83@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).