public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Re: PowerPC PIC vs. DLL TLS issues Date: Sun, 13 Oct 2019 22:44:00 -0000 [thread overview] Message-ID: <93370e8e7b406cf0aeedcf57cf457c07d6a2c7e6@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 93370e8e7b406cf0aeedcf57cf457c07d6a2c7e6 *** commit 93370e8e7b406cf0aeedcf57cf457c07d6a2c7e6 Author: Alan Modra <amodra@gmail.com> AuthorDate: Mon Oct 7 23:14:31 2019 +1030 Commit: Alan Modra <amodra@gmail.com> CommitDate: Mon Oct 7 23:23:21 2019 +1030 Re: PowerPC PIC vs. DLL TLS issues A bug crept into commit f749f26eea, which could cause linker segfaults when creating PIEs. This patch fixes it. * elf64-ppc.c (ppc64_elf_size_dynamic_sections): Do allocate space for local got non-tls relocs when PIE. diff --git a/bfd/ChangeLog b/bfd/ChangeLog index 607f37cfb2..72737181b0 100644 --- a/bfd/ChangeLog +++ b/bfd/ChangeLog @@ -1,3 +1,8 @@ +2019-10-07 Alan Modra <amodra@gmail.com> + + * elf64-ppc.c (ppc64_elf_size_dynamic_sections): Do allocate + space for local got non-tls relocs when PIE. + 2019-10-07 Alan Modra <amodra@gmail.com> * elflink.c (elf_fixup_link_order): Don't attempt to find diff --git a/bfd/elf64-ppc.c b/bfd/elf64-ppc.c index 842fc40f14..32ed81d98e 100644 --- a/bfd/elf64-ppc.c +++ b/bfd/elf64-ppc.c @@ -9814,7 +9814,9 @@ ppc64_elf_size_dynamic_sections (bfd *output_bfd, htab->elf.irelplt->size += rel_size; htab->got_reli_size += rel_size; } - else if (bfd_link_dll (info)) + else if (bfd_link_pic (info) + && !(ent->tls_type != 0 + && bfd_link_executable (info))) { asection *srel = ppc64_elf_tdata (ibfd)->relgot; srel->size += rel_size;
next reply other threads:[~2019-10-13 22:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-13 22:44 gdb-buildbot [this message] 2019-10-13 22:44 ` Failures on Ubuntu-Aarch64-m64, branch master gdb-buildbot 2019-10-14 0:17 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot 2019-10-14 1:08 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot 2019-10-19 5:44 ` Failures on Fedora-i686, " gdb-buildbot 2019-10-19 7:11 ` Failures on Fedora-x86_64-m64, " gdb-buildbot 2019-10-19 7:27 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot 2019-10-19 8:05 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-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=93370e8e7b406cf0aeedcf57cf457c07d6a2c7e6@gdb-build \ --to=gdb-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: linkBe 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).