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] sparc: Dump dynamic relocation info to the map file
Date: Sun, 08 Oct 2017 00:51:00 -0000 [thread overview]
Message-ID: <f0f07ad1825e9b7f539e410562993b25f76e5627@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT f0f07ad1825e9b7f539e410562993b25f76e5627 ***
Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: f0f07ad1825e9b7f539e410562993b25f76e5627
sparc: Dump dynamic relocation info to the map file
Dump dynamic relocation info to the map file when generating dynamic
relocation in read-only section relocations if -Map is used.
* elfxx-sparc.c (readonly_dynrelocs): Dump dynamic relocation
in read-only section with minfo.
(_bfd_sparc_elf_size_dynamic_sections): Likewise.
next reply other threads:[~2017-10-08 0:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 0:51 sergiodj+buildbot [this message]
2017-10-08 0:51 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
2017-10-08 0:51 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-10-08 0:53 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2017-10-08 0:56 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-10-08 1:13 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-10-08 1:23 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-10-08 1:30 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-10-08 1:31 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-10-08 1:47 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-10-08 1:57 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-10-08 2:22 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2017-11-02 19:15 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2017-11-03 1:44 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2017-11-03 8:11 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-11-03 8:54 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2017-11-13 9:45 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2017-11-13 18:59 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2017-11-14 6:13 ` Failures on Fedora-ppc64le-native-extended-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=f0f07ad1825e9b7f539e410562993b25f76e5627@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).