[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/21964] __start_SCN symbols aren't exported anymore
From: |
matz at suse dot de |
Subject: |
[Bug ld/21964] __start_SCN symbols aren't exported anymore |
Date: |
Mon, 14 Aug 2017 20:18:30 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=21964
--- Comment #8 from Michael Matz <matz at suse dot de> ---
You mean it shows an additional issue, I wasn't saying my patch is perfect,
merely that it fixes my reported problem. I think it's the same reason of why
the testcase ld-gc/pr20022 fails with the proposed patch.
bfd_elf_define_start_stop doesn't want to create a __start symbol
if there already exists a defined one in the hash table, even if that comes
from a dynamic object. Normal symbols would have gone through
_bfd_elf_merge_symbol, which would have overridden the definition from a
dynamic object with the one from regular files if the latter has non-default
visibility.
But bfd_elf_define_start_stop simply gives up, doesn't create the proper
local (hidden/protected whatever you want to call it) __start symbol and hence
resolves regular refs against the one from the dynamic object (invalidly so).
Looking at this, that ld-gc/pr20002 doesn't fail without the patch from comment
#4 is a nice thing, but I think it succeeds for the wrong reasons. Something
is fishy with how those start/stop symbols are created, IMHO.
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug ld/21964] New: __start_SCN symbols aren't exported anymore, matz at suse dot de, 2017/08/14
- [Bug ld/21964] __start_SCN symbols aren't exported anymore, matz at suse dot de, 2017/08/14
- [Bug ld/21964] __start_SCN symbols aren't exported anymore, hjl.tools at gmail dot com, 2017/08/14
- [Bug ld/21964] __start_SCN symbols aren't exported anymore, matz at suse dot de, 2017/08/14
- [Bug ld/21964] __start_SCN symbols aren't exported anymore, hjl.tools at gmail dot com, 2017/08/14
- [Bug ld/21964] __start_SCN symbols aren't exported anymore, matz at suse dot de, 2017/08/14
- [Bug ld/21964] __start_SCN symbols aren't exported anymore, hjl.tools at gmail dot com, 2017/08/14
- [Bug ld/21964] __start_SCN symbols aren't exported anymore, matz at suse dot de, 2017/08/14
- [Bug ld/21964] __start_SCN symbols aren't exported anymore, hjl.tools at gmail dot com, 2017/08/14
- [Bug ld/21964] __start_SCN symbols aren't exported anymore,
matz at suse dot de <=
- [Bug ld/21964] __start_SCN symbols aren't exported anymore, matz at suse dot de, 2017/08/14
- [Bug ld/21964] __start_SCN symbols aren't exported anymore, matz at suse dot de, 2017/08/14
- [Bug ld/21964] __start_SCN symbols aren't exported anymore, matz at suse dot de, 2017/08/14
- [Bug ld/21964] __start_SCN symbols aren't exported anymore, hjl.tools at gmail dot com, 2017/08/14
- [Bug ld/21964] Invalid entry point used for executables on Windows, freddy77 at gmail dot com, 2017/08/17
- [Bug ld/21964] Invalid entry point used for executables on Windows, cvs-commit at gcc dot gnu.org, 2017/08/21
- [Bug ld/21964] Invalid entry point used for executables on Windows, freddy77 at gmail dot com, 2017/08/21
- [Bug ld/21964] Invalid entry point used for executables on Windows, amodra at gmail dot com, 2017/08/22
- [Bug ld/21964] Invalid entry point used for executables on Windows, freddy77 at gmail dot com, 2017/08/22
- [Bug ld/21964] Invalid entry point used for executables on Windows, cvs-commit at gcc dot gnu.org, 2017/08/22