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] Ignore dynamic references on forced local symbols
Date: Thu, 11 Jan 2018 23:57:00 -0000 [thread overview]
Message-ID: <d664fd41e15f058aab41b70c567ad09f2fab1115@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT d664fd41e15f058aab41b70c567ad09f2fab1115 ***
Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: d664fd41e15f058aab41b70c567ad09f2fab1115
Ignore dynamic references on forced local symbols
We should ignore dynamic references on forced local symbols during
garbage collection since they can never be referenced dynamically.
bfd/
PR ld/22649
* elflink.c (bfd_elf_gc_mark_dynamic_ref_symbol): Ignore dynamic
references on forced local symbols.
ld/
PR ld/22649
* testsuite/ld-elf/pr22649-1.s: New file.
* testsuite/ld-elf/pr22649-2a.s: Likewise.
* testsuite/ld-elf/pr22649-2b.s: Likewise.
* testsuite/ld-elf/pr22649.msg: Likewise.
* testsuite/ld-elf/shared.exp: Run ld/22649 tests.
next reply other threads:[~2018-01-11 23:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 23:57 sergiodj+buildbot [this message]
2018-01-11 23:57 ` Failures on Fedora-i686, branch master sergiodj+buildbot
2018-01-12 0:02 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-01-12 0:20 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-01-12 0:20 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2018-01-12 0:31 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-01-12 0:56 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2018-01-12 4:16 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-12 4:58 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-01-12 5:40 ` 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=d664fd41e15f058aab41b70c567ad09f2fab1115@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).