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] Define __start/__stop symbols when there is only a dynamic def
Date: Fri, 26 Jan 2018 06:02:00 -0000	[thread overview]
Message-ID: <32253bb7963ac7caa166ec41e336372f2ffc03d4@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 32253bb7963ac7caa166ec41e336372f2ffc03d4 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 32253bb7963ac7caa166ec41e336372f2ffc03d4

Define __start/__stop symbols when there is only a dynamic def

This patch fixes a case where a user had a C-representable named
section in both the executable and shared libraries, and of course
wanted the size of the local section in the executable, not the
dynamic section.  It does mean that __start and __stop symbols don't
behave exactly like PROVIDEd symbols, but I think that's a reasonable
difference particularly since this is the way they used to behave.

	* elflink.c (bfd_elf_define_start_stop): Override symbols when
	they are defined dynamically.


             reply	other threads:[~2018-01-26  6:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-26  6:02 sergiodj+buildbot [this message]
2018-01-26  6:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-01-26  6:49 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-01-26  7:13 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2018-01-26  7:28 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-26  7:53 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2018-01-26  8:25 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-01-26  8:43 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-01-26  9:03 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2018-01-26  9:08 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-26  9:16 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-01-26  9:29 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-01-26  9:32 ` Failures on Fedora-x86_64-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=32253bb7963ac7caa166ec41e336372f2ffc03d4@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).