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] relocs_compatible test for gc-sections
Date: Mon, 30 Oct 2017 02:05:00 -0000	[thread overview]
Message-ID: <81742b83e9f25895eaaf3a07ac1651a4e9a68251@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 81742b83e9f25895eaaf3a07ac1651a4e9a68251 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 81742b83e9f25895eaaf3a07ac1651a4e9a68251

relocs_compatible test for gc-sections

I noticed when looking at pr22300 that before calling check_relocs we
have an elf_object_id test (added for pr11933) as well as the
relocs_compatible test.  I believe backend gc_mark_hook and
gc_sweep_hook ought to be protected similarly from being confused by
unexpected relocations (for example, both elf64-ppc.c and elf32-ppc.c
use _bfd_elf_relocs_compatible, so I think it would be possible for
the ppc64 gc_mark_hook to be presented with a ppc32 relocatable
object).

	* elflink.c (elf_gc_sweep): Test elf_object_id in addition to
	relocs_compatible.
	(bfd_elf_gc_sections): Likewise.


             reply	other threads:[~2017-10-30  2:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30  2:05 sergiodj+buildbot [this message]
2017-10-30  2:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-10-30  2:32 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2017-10-30  3:11 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-10-30  3:15 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-10-30  3:40 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-10-30  3:42 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-10-30  5:30 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-10-30  5:54 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-10-30  6:04 ` Failures on Fedora-x86_64-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=81742b83e9f25895eaaf3a07ac1651a4e9a68251@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).