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] Fix Common symbol override test fails
Date: Wed, 06 Dec 2017 08:32:00 -0000	[thread overview]
Message-ID: <65281396861dfcfa993eb5af4769d6837104890d@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 65281396861dfcfa993eb5af4769d6837104890d ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 65281396861dfcfa993eb5af4769d6837104890d

Fix Common symbol override test fails

Fixes fails on SH and NDS32 introduced by dyn_reloc tidy.

	* elf32-lm32.c (lm32_elf_check_relocs): Skip non-ALLOC sections.
	* elf32-m32r.c (m32r_elf_check_relocs): Likewise.
	* elf32-nds32.c (nds32_elf_check_relocs): Likewise.
	* elf32-or1k.c (or1k_elf_check_relocs): Likewise.
	* elf32-sh.c (sh_elf_check_relocs): Likewise.


             reply	other threads:[~2017-12-06  8:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06  8:32 sergiodj+buildbot [this message]
2017-12-06  8:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-12-06 12:24 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-12-06 12:46 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-12-06 12:52 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-12-06 13:07 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-12-06 13:12 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-12-06 13:20 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-12-06 16:06 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-12-06 19:36 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-12-06 20:02 ` Failures on Ubuntu-AArch32-native-gdbserver-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=65281396861dfcfa993eb5af4769d6837104890d@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).