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] Delete relocations associatesd with deleted exidx entries.
Date: Fri, 23 Sep 2016 19:06:00 -0000	[thread overview]
Message-ID: <5025eb7c0d87b01507116353b5d63b163d7add3d@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 5025eb7c0d87b01507116353b5d63b163d7add3d ***

Author: Akihiko Odaki <akihiko.odaki.4i@stu.hosei.ac.jp>
Branch: master
Commit: 5025eb7c0d87b01507116353b5d63b163d7add3d

Delete relocations associatesd with deleted exidx entries.

	PR ld/20595
ld	* testsuite/ld-arm/unwind-4.d: Add -q option to linker command
	line and -r option to objdump command line.  Match emitted relocs
	to make sure that superflous relocs are not generated.

bfd	* elf-bfd.h (struct elf_backend_data): Add
	elf_backend_count_output_relocs callback to count relocations in
	the final output.
	* elf-arm.c (elf32_arm_add_relocation): Deleted.
	(elf32_arm_write_section): Move additional relocation to emit_relocs.
	(elf32_arm_count_output_relocs): New function.
	(emit_relocs): New function.
	(elf32_arm_emit_relocs): New function.
	(elf32_arm_vxworks_emit_relocs): New function.
	(elf_backend_emit_relocs): Updated to use the new functions.
	(elf_backend_count_output_relocs): New define.
	* bfd/elflink.c (bfd_elf_final_link): Do not add additional_reloc_count
	to the relocation count.
	(_bfd_elf_link_size_reloc_section): Use callback to count the
	relocations which will be in output.
	(_bfd_elf_default_count_output_relocs): New function.
	* bfd/elfxx-target.h (elf_backend_count_output_relocs): New define.


             reply	other threads:[~2016-09-23 16:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-23 19:06 sergiodj+buildbot [this message]
2016-09-23 19:06 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-23 19:18 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-09-23 19:35 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-09-23 20:06 ` Failures on Debian-i686, " sergiodj+buildbot
2016-09-23 20:44 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2016-09-23 20:47 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-09-24  1:54 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-09-24  2:26 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot
2016-09-24  5:23 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-09-24  5:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-09-25 22:38 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-09-25 23:07 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-09-26  4:39 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-09-26  4:44 ` 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=5025eb7c0d87b01507116353b5d63b163d7add3d@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).