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] RISC-V: Fix relocation failure with zero address sections.
Date: Thu, 15 Feb 2018 22:04:00 -0000 [thread overview]
Message-ID: <09ca4b9d9bd61ecb779386a6cc7796cb05dde1af@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 09ca4b9d9bd61ecb779386a6cc7796cb05dde1af ***
Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 09ca4b9d9bd61ecb779386a6cc7796cb05dde1af
RISC-V: Fix relocation failure with zero address sections.
bfd/
* elfnn-riscv.c (_bfd_riscv_relax_section): Ifdef out check to ignore
symbols whose section address is zero.
next reply other threads:[~2018-02-15 22:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 22:04 sergiodj+buildbot [this message]
2018-02-15 22:05 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-02-15 22:08 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-02-15 22:10 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-02-15 22:14 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-02-15 22:15 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-02-15 22:29 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-15 22:30 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-02-15 22:38 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-02-15 23:11 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-16 0:20 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-02-16 0:52 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2018-02-17 11:48 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-02-28 5:35 ` Failures on Ubuntu-AArch64-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=09ca4b9d9bd61ecb779386a6cc7796cb05dde1af@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).