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] PR binutils/22875: MIPS/ELF: Also fail with relocation placeholders
Date: Wed, 04 Apr 2018 01:17:00 -0000 [thread overview]
Message-ID: <7ed6f92aaffdcc0995b0247379fb8ea621854dce@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 7ed6f92aaffdcc0995b0247379fb8ea621854dce ***
Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 7ed6f92aaffdcc0995b0247379fb8ea621854dce
PR binutils/22875: MIPS/ELF: Also fail with relocation placeholders
Do not consider placeholder EMPTY_HOWTO relocation entries valid in
`rtype_to_howto' MIPS handlers. Instead issue an unsupported relocation
type error and return a NULL howto as with relocations outside the three
ISA-specific min-max ranges.
bfd/
* elf32-mips.c (mips_elf32_rtype_to_howto): Also return
unsuccessfully for placeholder howtos.
* elf64-mips.c (mips_elf64_rtype_to_howto): Likewise.
* elfn32-mips.c (mips_elf_n32_rtype_to_howto): Likewise.
next reply other threads:[~2018-04-04 1:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 1:17 sergiodj+buildbot [this message]
2018-04-04 1:17 ` Failures on Debian-s390x-m64, branch master sergiodj+buildbot
2018-04-04 1:18 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2018-04-04 1:22 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-04-04 1:26 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-04-04 1:30 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-04-04 1:43 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-04-04 1:47 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-04-04 1:56 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-04-04 2:22 ` Failures on Ubuntu-AArch32-m32, " 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=7ed6f92aaffdcc0995b0247379fb8ea621854dce@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).