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] tile: Mark __tls_get_addr in gc_mark_hook
Date: Wed, 18 Oct 2017 23:22:00 -0000 [thread overview]
Message-ID: <8e354058532d48dce19fdf0b2e0653609a69f19e@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 8e354058532d48dce19fdf0b2e0653609a69f19e ***
Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 8e354058532d48dce19fdf0b2e0653609a69f19e
tile: Mark __tls_get_addr in gc_mark_hook
TLS_GD_CALL relocations implicitly reference __tls_get_addr. Since
elf_gc_mark_hook is called before check_relocs now, we need to call
_bfd_generic_link_add_one_symbol to mark __tls_get_addr for garbage
collection.
* elf32-tilepro.c (tilepro_elf_gc_mark_hook): Call
_bfd_generic_link_add_one_symbol to mark __tls_get_addr.
* elfxx-tilegx.c (tilegx_elf_gc_mark_hook): Likewise.
next reply other threads:[~2017-10-18 23:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 23:22 sergiodj+buildbot [this message]
2017-10-18 23:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-10-18 23:23 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-10-18 23:39 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-10-18 23:53 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-10-19 0:03 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-10-20 17:37 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-10-20 17:53 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-10-20 17:54 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-10-20 18:14 ` Failures on Fedora-x86_64-native-extended-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=8e354058532d48dce19fdf0b2e0653609a69f19e@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).