https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66912
--- Comment #4 from nsz at gcc dot gnu.org ---
Author: nsz
Date: Tue Oct 20 09:50:58 2015
New Revision: 229030
URL: https://gcc.gnu.org/viewcvs?rev=229030=gcc=rev
Log:
Fix default_binds_local_p_2 for extern protected data
Backport from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66912
nsz at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66912
--- Comment #3 from nsz at gcc dot gnu.org ---
Author: nsz
Date: Tue Oct 20 09:37:27 2015
New Revision: 229024
URL: https://gcc.gnu.org/viewcvs?rev=229024=gcc=rev
Log:
Fix default_binds_local_p_2 for extern protected data
gcc:
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66912
--- Comment #1 from Richard Earnshaw rearnsha at gcc dot gnu.org ---
Erm, isn't that the whole point of marking the symbol 'protected'?
From the ELF spec:
quote
STV_PROTECTED
A symbol defined in the current component is protected if it is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66912
--- Comment #2 from nsz at gcc dot gnu.org ---
protected only means it cannot be overridden.
so we know the symbol will be resolved to the local one,
however it may be visible externally and then the address
must be the same in the other modules
