[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug gold/18548] gold incorrectly exports start/stop symbols (GLOBAL)
From: |
cvs-commit at gcc dot gnu.org |
Subject: |
[Bug gold/18548] gold incorrectly exports start/stop symbols (GLOBAL) |
Date: |
Tue, 21 Jul 2015 23:11:03 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=18548
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot
gnu.org> ---
The master branch has been updated by Cary Coutant <address@hidden>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5417c94d1a944d1a27f99240e5d62a6d7cd324f1
commit 5417c94d1a944d1a27f99240e5d62a6d7cd324f1
Author: Cary Coutant <address@hidden>
Date: Tue Jul 21 16:10:05 2015 -0700
Fix problem where __start_ and __stop_ section symbols do not honor version
script.
When creating the special __start_ and __stop_ section symbols, gold
does not check the version script to see if they should be local
instead of global.
2015-07-21 Cary Coutant <address@hidden>
gold/
PR gold/18548
* symtab.cc (Symbol_table::do_define_in_output_data): Check for
forced local symbol even when oldsym != NULL.
(Symbol_table::do_define_in_output_segment): Likewise.
(Symbol_table::do_define_as_constant): Likewise.
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug gold/18548] gold incorrectly exports start/stop symbols (GLOBAL),
cvs-commit at gcc dot gnu.org <=