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: Print an error when unable to align a section
Date: Thu, 07 Sep 2017 17:56:00 -0000 [thread overview]
Message-ID: <9eb7b0acb54e18e7cbca196a8bdb320844a858b3@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 9eb7b0acb54e18e7cbca196a8bdb320844a858b3 ***
Author: Palmer Dabbelt <palmer@dabbelt.com>
Branch: master
Commit: 9eb7b0acb54e18e7cbca196a8bdb320844a858b3
RISC-V: Print an error when unable to align a section
This used to just print "can't relax section: Success", which is a silly
error message.
bfd/ChangeLog
2017-09-07 Palmer Dabbelt <palmer@dabbelt.com>
* elfnn-riscv.c (_bfd_riscv_relax_align): Call bfd_set_error and
print an error message when unable to relax a .align directive.
next reply other threads:[~2017-09-07 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 17:56 sergiodj+buildbot [this message]
2017-09-07 17:56 ` *** COMPILATION FAILED *** Failures on Ubuntu-AArch64-native-gdbserver-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2017-09-07 18:08 ` *** COMPILATION FAILED *** Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-09-07 18:20 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
2017-09-07 18:29 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2017-09-07 18:29 ` *** COMPILATION FAILED *** Failures on Ubuntu-AArch32-native-gdbserver-m32, branch master *** BREAKAGE *** sergiodj+buildbot
2017-09-07 18:30 ` *** COMPILATION FAILED *** Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2017-09-07 20:45 ` Failures on Fedora-x86_64-m32, branch master sergiodj+buildbot
2017-09-08 0:36 ` *** COMPILATION FAILED *** Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, branch master *** BREAKAGE *** sergiodj+buildbot
2017-09-08 0:36 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch master 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=9eb7b0acb54e18e7cbca196a8bdb320844a858b3@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).