https://sourceware.org/bugzilla/show_bug.cgi?id=25236
--- Comment #8 from cvs-commit at gcc dot gnu.org ---
The master branch has been updated by Alan Modra :
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5fa370e437f39bf73a133cc84c4e6329943522bf
commit 5fa370e437f39bf73a133cc84c4e6
https://sourceware.org/bugzilla/show_bug.cgi?id=25236
Alan Modra changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://sourceware.org/bugzilla/show_bug.cgi?id=25236
--- Comment #6 from Fangrui Song ---
To make sure we are on the same page. In the case that both a.o and a.so define
the common symbol:
The definition from a.o wins. --version-script should apply versions on the
definition. At runtime, the sh
https://sourceware.org/bugzilla/show_bug.cgi?id=25236
Ian Lance Taylor changed:
What|Removed |Added
CC||ian at airs dot com
--- Comment #5
https://sourceware.org/bugzilla/show_bug.cgi?id=25236
Alan Modra changed:
What|Removed |Added
CC||iant at google dot com
--
You are recei
https://sourceware.org/bugzilla/show_bug.cgi?id=25236
--- Comment #3 from Fangrui Song ---
Maybe we should discuss on the generic ABI mailing list. It is very late here
(01:00) so I'll not do that now. If you create a thread, can you CC me?
My feeling is that a STN_COMMON (STT_COMMON) definition
https://sourceware.org/bugzilla/show_bug.cgi?id=25236
--- Comment #4 from Alan Modra ---
No, I'm not saying a common in a shared library wins over a common in a regular
object, just that the maximum size is taken into account.
See the comment in bfd/elflink.c starting /* NEWDYNCOMMON and OLDDYNC
https://sourceware.org/bugzilla/show_bug.cgi?id=25236
Alan Modra changed:
What|Removed |Added
CC||amodra at gmail dot com
--- Comment #2 f
https://sourceware.org/bugzilla/show_bug.cgi?id=25236
--- Comment #1 from Fangrui Song ---
symbol versioning is always enabled. openmpi may need a workaround
https://github.com/open-mpi/ompi/issues/7209
--
You are receiving this mail because:
You are on the CC list for the bug.
