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] ELF/LD: Always consider STB_LOCAL symbols local
Date: Thu, 20 Apr 2017 16:50:00 -0000	[thread overview]
Message-ID: <0fad29560ee055f1253a8e40bfc09b413117480d@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 0fad29560ee055f1253a8e40bfc09b413117480d ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 0fad29560ee055f1253a8e40bfc09b413117480d

ELF/LD: Always consider STB_LOCAL symbols local

Do not require forced local (STB_LOCAL) symbols to have a definition in
a regular file to be considered to resolve local to the current module,
matching `elf_link_renumber_local_hash_table_dynsyms'.  In the absence
of a regular definition any reference to a STB_LOCAL symbol will have to
be garbage collected along with the undefined symbol itself, or the link
will eventually fail.  Either way the symbol concerned is not going to
be external.

	bfd/
	* elflink.c (_bfd_elf_symbol_refs_local_p): Always return TRUE
	if forced local.


             reply	other threads:[~2017-04-20 16:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 16:50 sergiodj+buildbot [this message]
2017-04-20 16:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-04-20 17:29 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-04-20 18:07 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-04-20 18:16 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-04-20 18:38 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-04-20 19:02 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-04-20 19:27 ` 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=0fad29560ee055f1253a8e40bfc09b413117480d@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).