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] Make __start/__stop symbols dynamic and add testcase
Date: Tue, 30 Jan 2018 00:09:00 -0000 [thread overview]
Message-ID: <36b8fda5d614cb5aaf701a92befa9919bd0b195a@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 36b8fda5d614cb5aaf701a92befa9919bd0b195a ***
Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 36b8fda5d614cb5aaf701a92befa9919bd0b195a
Make __start/__stop symbols dynamic and add testcase
bfd/
* elflink.c (bfd_elf_define_start_stop): Make __start and __stop
symbols dynamic.
ld/
* testsuite/ld-elf/pr21964-3a.c: New file.
* testsuite/ld-elf/pr21964-3c.c: New file.
* testsuite/ld-elf/shared.exp: Run new __start/__stop testcase.
next reply other threads:[~2018-01-30 0:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 0:09 sergiodj+buildbot [this message]
2018-01-30 0:09 ` Failures on Debian-s390x-m64, branch master sergiodj+buildbot
2018-01-30 0:15 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-01-30 0:15 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-01-30 0:24 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-01-30 0:24 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-01-30 0:27 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-30 0:33 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2018-01-30 0:37 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-30 0:38 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-01-30 0:47 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-01-30 1:09 ` 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=36b8fda5d614cb5aaf701a92befa9919bd0b195a@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).