https://sourceware.org/bugzilla/show_bug.cgi?id=18167
Alan Modra <amodra at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amodra at gmail dot com
--- Comment #2 from Alan Modra <amodra at gmail dot com> ---
Likely due to my PR 15228 fix.
HJ's advice is only reasonable if you have glibc and gcc changes that
a) make code generated for access to protected visibility variables in shared
libraries effectively be the same as for default visibility variables, and
b) you have glibc changes that ensure you keep the semantics of protected
visibility variables.
Otherwise all HJ's changes do is revert the PR 15228 fix, and you will silently
generate buggy executables that have a copy of a protected variable in .dynbss
that isn't used by the shared library defining that variable. ie. you've
broken the semantics of protected variables. If either the executable or the
shared library update the variable's value, then they see different values in a
variable that has only one definition.
I also think HJ's linker changes are unsafe since there is no attempt to detect
shared libraries that are compiled without the as yet uncommitted gcc changes.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
