[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/25236] common symbol: don't consider definitions in shared objec
From: |
amodra at gmail dot com |
Subject: |
[Bug ld/25236] common symbol: don't consider definitions in shared objects |
Date: |
Fri, 06 Dec 2019 12:29:56 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=25236
--- Comment #4 from Alan Modra <amodra at gmail dot com> ---
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 OLDDYNCOMMON
indicate .. It's interesting that the comment mentions fortran too.
I believe this is Ian's code from 1997 or so. See also
https://www.airs.com/blog/archives/49
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug ld/25236] common symbol: don't consider definitions in shared objects, amodra at gmail dot com, 2019/12/05
- [Bug ld/25236] common symbol: don't consider definitions in shared objects,
amodra at gmail dot com <=
- [Bug ld/25236] common symbol: don't consider definitions in shared objects, i at maskray dot me, 2019/12/06
- [Bug ld/25236] common symbol: don't consider definitions in shared objects, amodra at gmail dot com, 2019/12/06
- [Bug ld/25236] common symbol: don't consider definitions in shared objects, ian at airs dot com, 2019/12/06
- [Bug ld/25236] common symbol: don't consider definitions in shared objects, i at maskray dot me, 2019/12/06
- [Bug ld/25236] common symbol: don't consider definitions in shared objects, amodra at gmail dot com, 2019/12/06
- [Bug ld/25236] common symbol: don't consider definitions in shared objects, cvs-commit at gcc dot gnu.org, 2019/12/07