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] Don't check R_386_GOT32 when setting need_convert_load Date: Fri, 20 May 2016 17:00:00 -0000 [thread overview] Message-ID: <52bf37dd91e5dd983ed20d1329293d077fe71e41@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 52bf37dd91e5dd983ed20d1329293d077fe71e41 *** Author: H.J. Lu <hjl.tools@gmail.com> Branch: master Commit: 52bf37dd91e5dd983ed20d1329293d077fe71e41 Don't check R_386_GOT32 when setting need_convert_load Since we no longer convert R_386_GOT32, don't check R_386_GOT32 when setting need_convert_load. * elf32-i386.c (elf_i386_check_relocs): Don't check R_386_GOT32 when setting need_convert_load.
next reply other threads:[~2016-05-20 17:00 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-05-20 17:00 sergiodj+buildbot [this message] 2016-05-20 17:00 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot 2016-05-20 17:02 ` Failures on Debian-i686, " sergiodj+buildbot 2016-05-20 17:02 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2016-05-20 17:12 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot 2016-05-20 17:12 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot 2016-05-20 17:13 ` Failures on Fedora-i686, " sergiodj+buildbot 2016-05-20 17:14 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2016-05-20 17:19 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-05-20 17:32 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2016-05-20 17:43 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot 2016-05-20 18:04 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-05-20 18:43 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2016-05-20 19:04 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " 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=52bf37dd91e5dd983ed20d1329293d077fe71e41@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).