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] Work around sparc glibc bug Date: Fri, 08 Dec 2017 21:57:00 -0000 [thread overview] Message-ID: <a9d44aad42e127adadbad35f23931d8d83aa40c1@gdb-build> (raw) *** TEST RESULTS FOR COMMIT a9d44aad42e127adadbad35f23931d8d83aa40c1 *** Author: Alan Modra <amodra@gmail.com> Branch: master Commit: a9d44aad42e127adadbad35f23931d8d83aa40c1 Work around sparc glibc bug * elfxx-sparc.c (_bfd_sparc_elf_relocate_section): When emitting dynamic R_SPARC_RELATIVE for GOT entries, ensure the section contents are zeroed.
next reply other threads:[~2017-12-08 21:57 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-12-08 21:57 sergiodj+buildbot [this message] 2017-12-08 21:57 ` Failures on Fedora-x86_64-m32, branch master sergiodj+buildbot 2017-12-08 22:02 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-12-08 22:13 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-12-08 22:17 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-12-08 22:26 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-12-08 22:29 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-12-08 22:32 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-12-08 23:49 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-12-09 0:19 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-12-09 1:49 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-12-09 2:37 ` Failures on Ubuntu-AArch32-native-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=a9d44aad42e127adadbad35f23931d8d83aa40c1@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: 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).