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] AArch64: Revert setting of elf class in linker stub. Date: Fri, 10 Jan 2020 14:52:00 -0000 [thread overview] Message-ID: <8cd0e5e93145699736a370b271ff03f3f41670b0@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 8cd0e5e93145699736a370b271ff03f3f41670b0 *** commit 8cd0e5e93145699736a370b271ff03f3f41670b0 Author: Tamar Christina <tamar.christina@arm.com> AuthorDate: Fri Jan 10 13:48:57 2020 +0000 Commit: Tamar Christina <tamar.christina@arm.com> CommitDate: Fri Jan 10 13:51:08 2020 +0000 AArch64: Revert setting of elf class in linker stub. This changes the fix to PR 25210 by removing the ELF class change. As it turns out the correct change was only the change in compress.c. Everything else is unneeded and setting the elf class is making the linker behave very oddly under LTO. The first stub is correctly written out but for the rest the suddenly don't have a pointer to the stub section anymore. This caused SPEC to fail as the program would branch to the stub and it wouldn't be filled in. Committed to master under the trivial rule as this is partially reverting a previous commit. bfd/ChangeLog: PR 25210 * elfnn-aarch64.c (_bfd_aarch64_create_stub_section): Remove elfclass. diff --git a/bfd/ChangeLog b/bfd/ChangeLog index 68b15198b1..2aba654826 100644 --- a/bfd/ChangeLog +++ b/bfd/ChangeLog @@ -1,3 +1,8 @@ +2020-01-10 Tamar Christina <tamar.christina@arm.com> + + PR 25210 + * elfnn-aarch64.c (_bfd_aarch64_create_stub_section): Remove elfclass. + 2020-01-10 Alan Modra <amodra@gmail.com> * coff-alpha.c (alpha_ecoff_object_p): Calculate size in bfd_size_type. diff --git a/bfd/elfnn-aarch64.c b/bfd/elfnn-aarch64.c index 756ffeb6bd..5fabcd8f64 100644 --- a/bfd/elfnn-aarch64.c +++ b/bfd/elfnn-aarch64.c @@ -3177,10 +3177,6 @@ _bfd_aarch64_create_stub_section (asection *section, if (s_name == NULL) return NULL; - /* PR 25210. Set the right class on the stub_bfd. */ - elf_elfheader (htab->stub_bfd)->e_ident[EI_CLASS] = ELFCLASSNN; - BFD_ASSERT (ELFCLASSNN == get_elf_backend_data (htab->stub_bfd)->s->elfclass); - memcpy (s_name, section->name, namelen); memcpy (s_name + namelen, STUB_SUFFIX, sizeof (STUB_SUFFIX)); return (*htab->add_stub_section) (s_name, section);
next reply other threads:[~2020-01-10 14:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-10 14:52 gdb-buildbot [this message] 2020-01-10 14:52 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, branch master gdb-buildbot 2020-01-10 15:09 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot 2020-01-11 1:37 ` Failures on Fedora-i686, " gdb-buildbot 2020-01-11 1:52 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot 2020-01-11 2:20 ` Failures on Fedora-x86_64-m32, " gdb-buildbot 2020-01-11 2:24 ` Failures on Fedora-x86_64-m64, " gdb-buildbot 2020-01-11 3:00 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot 2020-01-11 3:16 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot 2020-01-11 3:47 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot 2020-01-11 3:54 ` Failures on Fedora-x86_64-native-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=8cd0e5e93145699736a370b271ff03f3f41670b0@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).